You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How much work would a CI Build plugin be to create (basically the inverse of this plugin)?/What is required to actually bundle a plugin for Jenkins? I feel like I could create the plugin fairly easily from your source. Then it is just a matter of getting it in.
We use the gitflow coding model (feature branches) and then use Jenkins to merge completed (and tested) branches back into develop, but sometimes people push a feature branch to git so they can try out the features or demo potential features to others without wanting them compiled into develop yet so I would like to tag a commit with ci build or something like that to say this feature is ready to be shipped to develop which would cause a Jenkins build and merge assuming everything passed.
The text was updated successfully, but these errors were encountered:
How much work would a CI Build plugin be to create (basically the inverse of this plugin)?/What is required to actually bundle a plugin for Jenkins? I feel like I could create the plugin fairly easily from your source. Then it is just a matter of getting it in.
We use the gitflow coding model (feature branches) and then use Jenkins to merge completed (and tested) branches back into develop, but sometimes people push a feature branch to git so they can try out the features or demo potential features to others without wanting them compiled into develop yet so I would like to tag a commit with ci build or something like that to say this feature is ready to be shipped to develop which would cause a Jenkins build and merge assuming everything passed.
The text was updated successfully, but these errors were encountered: