-
Notifications
You must be signed in to change notification settings - Fork 400
[JENKINS-27136] Workflow support for GitHub Push Triggers #59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
pom.xml
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reason?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The minimun Workflow compatible core version is 1.580.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
compatible with what?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any Workflow related feature requires core 1.580.X. Since I'm adding Workflow compatibility, the plugin requires 1.580.X now.
See https://github.com/jenkinsci/workflow-plugin/blob/master/README.md#installation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't mean that you must update core dependencies in non workflow plugins
SCMTriggerItem was added in 1.568. 1.580.x is the next LTS after that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And this is right answer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@amuniz a tip: if you change this line to
<version>1.580.1</version> <!-- first LTS after SCMTriggerItem -->then this whole comment thread becomes hidden by default. :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jglick 🙀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
facepalm
|
This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation. |
|
I'm realy after this ... 👍 |
|
👎 until #57 will be merged. Also this change looks like breaking interfaces change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
formating
|
@KostyaSha the only way to make this compatible with Workflow jobs is changing interfaces. Not sure how this impact in #57 |
|
please wait for #57 because of hard rebase process instead |
|
@amuniz for the methods that were modified, maybe you could override them instead, deprecating the old method signatures? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you'll need to add a null check on Jenkins.getInstance(). Otherwise, we'll be getting FindBugs errors I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
new jenkins has getJenkinsInstance instead
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Starting from 1.596 only AFAIK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then just copy-paste it realisation and put to static function imho.
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please don't collapse in one line, really difficult read.
…h JenkinsRule load
…on is required) + fix test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will be a CCE if it is not in fact a ParameterizedJob. 🐛
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another place where the 1.621 method would be nicer.
|
🐝 |
|
🐝 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems we need the withBridgeMethods magic here as well
|
@amuniz |
|
i'm ok to merge it. But @KostyaSha thinks that bumping core version before all other useful PRs will be closed on current core version may cause this plugin unusable for older jenkins instances. (it should be squashed to limited set of commits before merge happens, as of 30 commits for such small change is strange, but please wait until green light) |
|
If the plugin maintainer desires commit squashing I would suggest that be done as part of the merge rather than destroying history in the PR itself. |
|
@jglick i can suggest you firstly work with recena and amuniz PRs in CB forks and only after review send to maintainers. Never saw in jenkinsci PRs with so many commits and issues before. Back to upstream repos when their PRs wouldn't have "child" issues. @oleg-nenashev could you say what exactly was broken for you in last releases? |
|
@KostyaSha just ask for squash before you are going to merge, I'll do it. The current amount of revisions and comments in every PR is hopefully going to significantly increase the code base quality in the Jenkins community in general. Moreover, I think is quite good for other developers to have all this review information available publicly, since it is, from my point if view, a nice source of knowledge. |
|
@amuniz CB pays you for your work, but it doesn't mean that CB that hired and locked all possible jenkins related devs must lock jenkins activities on their internal plans/needs. This noise is waste of time for FOSS devs, instead of working on new features and other plugins i'm getting 100 comments with newbie errors. Compare to @jglick PRs that doesn't require many discussions. I will back to this PR when we resolve other planned features/fixes and will be ok with core bump. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change makes the Javadoc comment in line 133 obsolete, and without that, AbstractProject is an unused import as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@daniel-beck thanks. Fixed.
Conflicts: src/main/java/org/jenkinsci/plugins/github/config/GitHubPluginConfig.java
|
Merge conflicts resolved. |
|
@amuniz please don't rebase. We have 3 or 4 prs in "must have" queue before we are going to merge this pr. I'll do the rebase by myself when the time will come |
|
@lanwen ok. If you face some issue while merging, ping me. |
|
@lanwen is there any pending PR blocking this to merge yet? |
|
@amuniz core update blocks it. |
|
@KostyaSha could you elaborate please? What's wrong with the core update? |
|
1.554.1 (2014/04/30)
|
|
no, think generic trigger is too complex to move workflow in queue. And while git-plugin of new version is already depends on core version with workflow think we should try to merge this. |
|
ok, as you wish, i tired from this workflow spam |
|
please review #82 |
|
Merged in #82 |
https://issues.jenkins-ci.org/browse/JENKINS-27136
Currently Workflow jobs can not be triggered when a GitHub push hook is received, this PR makes it possible.
In this document there is information about the required changes in plugins to make them compatible with Workflow. This changes have been applied here.
@reviewbybees