[JIRA] (JENKINS-37871) Credentials-binding plugin is executed after pre-release build steps of release-plugin
Title: Message Title Christian Lipphardt commented on JENKINS-37871 Re: Credentials-binding plugin is executed after pre-release build steps of release-plugin Created https://github.com/jenkinsci/credentials-binding-plugin/pull/21 as fix. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37871) Credentials-binding plugin is executed after pre-release build steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials-binding plugin is executed after pre-release build steps of release-plugin Change By: Christian Lipphardt Summary: Credentials-binding plugin is executed after prebuild pre-release build steps of release-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37871) Credentials-binding plugin is executed after prebuild steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials-binding plugin is executed after prebuild steps of release-plugin Change By: Christian Lipphardt h5. ProblemInjecting credentials through the credentials-binding plugin is done too late when using the prebuild steps of the release-plugin. The credentials-binding plugin is executed after the prebuild steps of the release-plugin, so any injected credentials cannot be used it.h5. Steps to reproduce* Inject a secret through the credentials-binding plugin* Enable 'configure a release' build wrapper* Configure the release-plugin with a pre-release shell step, which echoes the injected secret to build log* Create a normal shell build step which echoes the injected secret to build logSee [^trigger-release-build.txt] for an output of the above steps.You see that the injected secret is not available in the pre-release step of the release-plugin buildwrapper, but it is in the normal build step.h5. Expected behaviorAs a user, I can inject the credentials and use them with the prebuild pre-release steps of the release-plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37871) Credentials-binding plugin is executed after prebuild steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials-binding plugin is executed after prebuild steps of release-plugin Change By: Christian Lipphardt h5. ProblemInjecting credentials through the credentials-binding plugin is done too late when using the prebuild steps of the release-plugin. The credentials-binding plugin is executed after the prebuild steps of the release-plugin, so any injected credentials cannot be used it.h5. Steps to reproduce * Inject a secret through the credentials-binding plugin * Enable 'configure a release' build wrapper * Configure the release-plugin with a pre-release shell step, which echoes the injected secret to build log* Create a normal shell build step which echoes the injected secret to build logSee [^trigger-release-build.txt] for an output of the above steps.You see that the injected secret is not available in the pre-release step of the release-plugin buildwrapper, but it is in the normal build step. h5. Expected behaviorAs a user, I can inject the credentials and use them with the prebuild steps of the release - plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37871) Credentials-binding plugin is executed after prebuild steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials-binding plugin is executed after prebuild steps of release-plugin Change By: Christian Lipphardt Attachment: trigger-release-build.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37871) Credentials-binding plugin is executed after prebuild steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials-binding plugin is executed after prebuild steps of release-plugin Change By: Christian Lipphardt h5. ProblemInjecting credentials through the credentials-binding plugin is done too late when using the prebuild steps of the release-plugin. The credentials-binding plugin is executed after the prebuild steps of the release-plugin, so any injected credentials cannot be used it.h5. Steps to reproduceh5. Expected behaviour behavior As a user, I can inject the credentials and use them with the prebuild steps of the release plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37871) Credentials binding plugin is executed after prebuild steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials binding plugin is executed after prebuild steps of release-plugin Change By: Christian Lipphardt Summary: Credentials binding plugin is executed after Release Wrapper prebuild steps of release-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37871) Credentials-binding plugin is executed after prebuild steps of release-plugin
Title: Message Title Christian Lipphardt updated an issue Jenkins / JENKINS-37871 Credentials-binding plugin is executed after prebuild steps of release-plugin Change By: Christian Lipphardt Summary: Credentials - binding plugin is executed after prebuild steps of release-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37871) Credentials binding plugin is executed after Release Wrapper
Title: Message Title Christian Lipphardt created an issue Jenkins / JENKINS-37871 Credentials binding plugin is executed after Release Wrapper Issue Type: Bug Assignee: Jesse Glick Components: credentials-binding-plugin Created: 2016/Aug/31 9:04 PM Environment: Jenkins 1.609.3 release-plugin:2.5.4 credentials-binding-plugin:1.9 Priority: Minor Reporter: Christian Lipphardt Problem Injecting credentials through the credentials-binding plugin is done too late when using the prebuild steps of the release-plugin. The credentials-binding plugin is executed after the prebuild steps of the release-plugin, so any injected credentials cannot be used it. Expected behaviour As a user, I can inject the credentials and use them with the prebuild steps of the release plugin. Add Comment
[JIRA] [build-pipeline-plugin] (JENKINS-28358) Console Window doesn't show
Title: Message Title Christian Lipphardt commented on JENKINS-28358 Re: Console Window doesn't show I got the same problem when I try to start a pipeline build Uncaught TypeError: Cannot read property 'msie' of undefined Uncaught TypeError: jQuery.fancybox is not a function Jenkins version: 1.596.3 Build-Pipeline plugin: 1.4.7 JQuery plugin: 1.11.2-0 Browser: Chrome 43.0.2357.124 (64-bit) OSX Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-18490) Run button not work
Christian Lipphardt commented on JENKINS-18490 Run button not work I did a quick research. Run button works with jobs which require no parameters, jobs with parameters do not work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17769) GitSCM.skipTag is broken in GitPublisher
Christian Lipphardt commented on JENKINS-17769 GitSCM.skipTag is broken in GitPublisher I have the same issue: Reproduce: Add git repos Check 'merge before build' Check 'skip internal tag' Add 'Git Publisher' as postbuild step Check 'Push Only If Build Succeeds' Check 'Merge Results' Run build -- Error ERROR: Failed to push merge to origin repository [8mha:WB+LCABb85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA= [0mhudson.plugins.git.GitException: Could not delete tag jenkins-test0-1 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.deleteTag(CliGitAPIImpl.java:901) at hudson.plugins.git.GitAPI.deleteTag(GitAPI.java:212) at hudson.plugins.git.GitPublisher$2.invoke(GitPublisher.java:237) at hudson.plugins.git.GitPublisher$2.invoke(GitPublisher.java:223) at hudson.FilePath.act(FilePath.java:839) at hudson.FilePath.act(FilePath.java:821) at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:223) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:685) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:632) at hudson.model.Run.run(Run.java:1463) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: hudson.plugins.git.GitException: Command "git tag -d jenkins-test0-1" returned status code 1: stdout: stderr: error: tag 'jenkins-test0-1' not found. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:774) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:740) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:750) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.deleteTag(CliGitAPIImpl.java:899) ... 15 more Pushing HEAD to branch integration at repo origin Build step 'Git Publisher' changed build result to FAILURE Build step 'Git Publisher' marked build as failure Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-17555) Environment variables not set early enough (or at all?)
Christian Lipphardt edited a comment on JENKINS-17555 Environment variables not set early enough (or at all?) I am also affected by this bug. I am using the plugin to inject a config file and then link the location of it via a variable as a parameter in a maven 2/3 job. It is not resolved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-17555) Environment variables not set early enough (or at all?)
Christian Lipphardt commented on JENKINS-17555 Environment variables not set early enough (or at all?) I am also affected by this bug. We are using the plugin to inject a config file and then link the location of it via a variable as a parameter in a maven 2/3 job. It is not resolved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Christian Lipphardt commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Same here. Please fix it! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Christian Lipphardt edited a comment on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Same here. Please fix it! (We can live with the fix to disable the internal tag for the moment tho) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
