Hi All, I have created a manual action at the end of my gitlabci pipeline that I call "release".
When this release target is invoked, I will spawn gradle to run the gradle-release <https://github.com/researchgate/gradle-release> plugin. This will - Remove the "-SNAPSHOT" qualified of the version in the root gradle.properties file - Commit the change to gradle.properties - Create a tag - Increment the version number and re-add a "-SNAPSHOT" qualifier to the gradle.properties - Commit gradle.properties The gradle-release plugin is mightily upset, because it is not on a branch. How can I have gitlabci tasks make changes to repository files, create tabs, etc. when there is no checked-out branch? Any input would be greatly appreciated. -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/0b5c66bb-b8e7-4fea-9017-7d788e1721f1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
