[JIRA] (JENKINS-37701) Manual trigger not running in build pipeline
Title: Message Title DEREK LU commented on JENKINS-37701 Re: Manual trigger not running in build pipeline Good to hear that you have it working. It is the Full project name that you can directly copy from the reference job. Once you open the job the Full name (with path) is displayed under the Project 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-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU commented on JENKINS-38670 Re: ability to enter build notes/parameters for a Manual step in the pipeline I did uploaded three screenshots from my workaround when I open this request. Please see the attachment of the One is to configure the ability; Another one is a button/link in the pipeline job to popup a window (job as work around) to enter a note The third one is the job to create the note. I put the links of the screenshots here: https://issues.jenkins-ci.org/secure/attachment/34222/Build_note_config_option.jpg https://issues.jenkins-ci.org/secure/attachment/34218/Build_note_for_manual_build.jpg https://issues.jenkins-ci.org/secure/attachment/34221/popup_from_build_note_link.jpg It would be nice if the entering note feature is part of the job itself rather than a separated job like I did in the workaround. Thanks 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-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU commented on JENKINS-38670 Re: ability to enter build notes/parameters for a Manual step in the pipeline Dan, Thanks for looking into this. As long as the notes can be accessed in the job at run/build time, it should be good enough, as we can add steps in the job to store the notes. In my workaround (with a separated job), I wrote scripts to save the notes/comments into files then compose them into an HTML file, then move the html file under user Content for viewing. I downloaded https://github.com/jenkinsci/build-pipeline-plugin/tree/JENKINS-38670. after buit and installed, I didn't see note entering ability in the build pipeline, so I guess the change for the feature is not in yet. Thanks. Derek 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-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_config_option.jpg 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-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_option_config.jpg 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-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_option_config.jpg 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-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_for_manual_build.jpg 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-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_option_config.jpg Attachment: Build_note_for_manual_build.jpg Attachment: popup_from_build_note_link.jpg Wish the following new feature can be added to the Build Pipeline Plugin:Add an option to show Build Note for Manual Build in the configuration. If the option is checked, a build note link will be displayed besides the trigger button, which can pop up a buildPipeline.fillDialog window for the user to enter values for parameters.I added this ability in my local with using another job (configured as a parameter) for entering build note . Please see the attached screenshots. It would be nice if the note can be entered to build job directly. It would be helpful if such an ability can be provided in a formal release.Thanks.Derek  Add Comment
[JIRA] (JENKINS-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_for_manual_build.jpg 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-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_option_config.jpg 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-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU created an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Issue Type: New Feature Assignee: Unassigned Components: build-pipeline-plugin Created: 2016/Oct/03 8:50 PM Priority: Major Reporter: DEREK LU Wish the following new feature can be added to the Build Pipeline Plugin: Add an option to show Build Note for Manual Build in the configuration. If the option is checked, a build note link will be displayed besides the trigger button, which can pop up a buildPipeline.fillDialog window for the user to enter values for parameters. I added this ability in my local with using another job (configured as a parameter) for entering build note . Please see the attached screenshots. It would be nice if the note can be entered to build job directly. It would be helpful if such an ability can be provided in a formal release. Thanks. Derek   
[JIRA] (JENKINS-27238) Inject parameters on manual build trigger
Title: Message Title DEREK LU commented on JENKINS-27238 Re: Inject parameters on manual build trigger I also hope this can be a standard functionality. Currently I customized the plugin in my local to do something like this. I create pull Provide an ability to enter build notes/parameters for a Manual step in the pipeline here and wish it can be developed as a standard functionality (not with a separated job, I use a separated job to play with the parameters) https://github.com/geoffbullen/build-pipeline-plugin/pull/4 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-37701) Manual trigger not running in build pipeline
Title: Message Title DEREK LU commented on JENKINS-37701 Re: Manual trigger not running in build pipeline I'm doing the same thing with 2.7.2 with build pipeline plugin 1.5.4 and it works fine. In Build Other Projects (manual step) specify Downstream Project Names without the leading /, for example Project/BuildJobs/Manual_Test if you do Denis/job-name it should work 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-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title DEREK LU commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job I made some change in my local as a customized workaround. Also I created a poll request "Provide an ability to enter build notes/parameters for a Manual step in the pipeline" https://github.com/geoffbullen/build-pipeline-plugin/pull/4 Hope it can be developed and included in a formal release. 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-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title DEREK LU commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job The Pipeline as code can promote for parameter value input, but it holds the executor. Our use case is to provide approval note from one stage to another, which may happen several days later. I have implemented a workaround in our case for now. Let the Manual Approving Job check a file parameter to decide to move forward or not. Then created another job to accept values for the parameter and save it to a file. In the Build pipeline, a string parameter is used to create a link to the parameter entering job, and it is displayed in the reversion box. the links is like Enter Parameters This will popup the job in a lightbox within the build pipeline. It is complicated and just a workaround. We really hope if this issue can get fixed soon. 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-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title DEREK LU commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job We have a use case to manually start job (from build pipeline) with prompting the user to input values for parameters. is there a plan to have this fixed? Thanks. 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] [git] (JENKINS-23450) Initial checkout doesn't create directory listed in Check out to a sub-directory
Derek Douville
commented on JENKINS-23450
Initial checkout doesnt create directory listed in Check out to a sub-directory
I figured out now that to get $GIT_BRANCH recognized in the subdirectory field, you can NOT use { } (that is, ${GIT_BRANCH} will fail, but $GIT_BRANCH succeeds). Thus, now, we are able to checkout to a subdirectory in the workspace at $GIT_BRANCH/src and then in the build script, cd into $WORKSPACE/GIT_BRANCH/src and go ahead and build.
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/d/optout.
[JIRA] [git] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Derek Douville
commented on JENKINS-20427
Build Parameter variable in branch name causes polling to detect false changes in GIT
I've been struggling with the same problem all week.
What I've determined is that the git plugin is either ignoring any variables created in Parameterized Build, or they are not getting passed. However, Parameterized Build can override variables the Git Plugin cares about.
Environment:
Use separate directories for workspace set to $GIT_BRANCH/src
Delete workspace Force Clone
Test Case 1: Override GIT_BRANCH
If you create a GIT_BRANCH parameter and run a build with garbage text, you can see the github plugin use that text (by the way, overriding GIT_BRANCH is bad, because it will override all of your automatic github push triggers too). This test shows that Parameterized Build at least runs before the git plugin uses its GIT_BRANCH variable.
Test Case 2: Create a new variable "MYBRANCH", specify $MYBRANCH as the branch to build.
If you now run a paramarized build and set this with some garbage (eg. not a real branch), the git clone should fail. But $MYBRANCH is treated as whitespace because it doesn't exist to the git plugin, thus performing default build behavior and building the last branch to get an update.
Test Case 3: Wrap MYBRANCH with curly braces ${MYBRANCH}
No difference
Test Case 4: Put garbage directly into the branch to build path
Type "asdasd" into the branch to build and see the build fail.
I also then added the EnvInject plugin and attempted to set the GIT_BRANCH variable from there, based on another variable's value, to no success.
My conclusion is that the Git plugin is not evaluating any environment variables passed into the branch specifications. This basically means parameterized builds are useless.
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/d/optout.
[JIRA] [git] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Derek Douville
edited a comment on JENKINS-20427
Build Parameter variable in branch name causes polling to detect false changes in GIT
I've been struggling with the same problem all week.
What I've determined is that the git plugin is either ignoring any variables created in Parameterized Build, or they are not getting passed. However, Parameterized Build can override variables the Git Plugin cares about.
Environment:
Use separate directories for workspace set to $GIT_BRANCH/src
Delete workspace Force Clone
Git Plugin: 2.2.2
Git Client Plugin: 1.10
GitHub API Plugin: 1.55
GitHub Plugin: 1.90
Test Case 1: Override GIT_BRANCH
If you create a GIT_BRANCH parameter and run a build with garbage text, you can see the github plugin use that text (by the way, overriding GIT_BRANCH is bad, because it will override all of your automatic github push triggers too). This test shows that Parameterized Build at least runs before the git plugin uses its GIT_BRANCH variable.
Test Case 2: Create a new variable "MYBRANCH", specify $MYBRANCH as the branch to build.
If you now run a paramarized build and set this with some garbage (eg. not a real branch), the git clone should fail. But $MYBRANCH is treated as whitespace because it doesn't exist to the git plugin, thus performing default build behavior and building the last branch to get an update.
Test Case 3: Wrap MYBRANCH with curly braces ${MYBRANCH}
No difference
Test Case 4: Put garbage directly into the branch to build path
Type "asdasd" into the branch to build and see the build fail.
I also then added the EnvInject plugin and attempted to set the GIT_BRANCH variable from there, based on another variable's value, to no success.
My conclusion is that the Git plugin is not evaluating any environment variables passed into the branch specifications. This basically means parameterized builds are useless.
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/d/optout.
[JIRA] [git] (JENKINS-23450) Initial checkout doesn't create directory listed in Check out to a sub-directory
Derek Douville
commented on JENKINS-23450
Initial checkout doesnt create directory listed in Check out to a sub-directory
Before I upgraded my github plugin yesterday, checking out to a subdir of ${GIT_BRANCH}/src was working. After upgrading, this fails. Even worse, since the build script does a "cd ${GIT_BRANCH}/src" and succeeds for projects that were building before the upgrade, it means we're building old source code.
New jobs that have never been built fail with the error posted in the bug description on the first run. Checkouts seem to succeed later because literally in ~jenkins/jobs/job/workspace a directory called "${GIT_BRANCH}" has been created.
So now, using $GIT_BRANCH is impossible for sub-directories. This is a more serious bug to me, I don't have a work around because we build multiple branches in the same workspace.
Help!
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/d/optout.
