[JIRA] [active-directory-plugin] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Title: Message Title Francesco Pagetti commented on JENKINS-22358 Re: Jenkins 1.556 gives 'Error 404 Not Found' This happens also on JBoss EAP7 as htpps sessions in URL are enabled by default. I submitted a pull request to disable the jsessionid in deployments of Jenkins on jboss. https://github.com/jenkinsci/jenkins/pull/2003 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] [core] (JENKINS-32587) Items in Jenkins should not expose Delete as a generic action, especially not basic jobs
Title: Message Title gus reiber commented on JENKINS-32587 Re: Items in Jenkins should not expose Delete as a generic action, especially not basic jobs instead, it should be part of the item configuration. 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] [htmlpublisher-plugin] (JENKINS-32281) HTML report shows "Checksum mismatch"
Title: Message Title Dave Ferran commented on JENKINS-32281 Re: HTML report shows "Checksum mismatch" windows-1252 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] [core] (JENKINS-32587) Items in Jenkins should not expose Delete as a generic action, especially not basic jobs
Title: Message Title gus reiber created an issue Jenkins / JENKINS-32587 Items in Jenkins should not expose Delete as a generic action, especially not basic jobs Issue Type: Improvement Assignee: Unassigned Components: core Created: 25/Jan/16 3:19 AM Priority: Minor Reporter: gus reiber Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [cloudbees-folder-plugin] (JENKINS-32585) Deleting a folder should not be shown in the 'actions' menu on the left, but instead should be part of the folder config
Title: Message Title gus reiber commented on JENKINS-32585 Re: Deleting a folder should not be shown in the 'actions' menu on the left, but instead should be part of the folder config Ideally, this would be true for all delete actions for all item types. Instead of delete being treated as a first class action, it should be pushed down to a configuration option to help trim the goop in the left menu. 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] [cloudbees-folder-plugin] (JENKINS-32586) Move "Delete Job" link to Job configuration screen
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-32586 Move "Delete Job" link to Job configuration screen Change By: James Dumay Users have given us feedback that the *Delete Job* link is a bit too close to the *Build Now* link. As deleting a Job is not a common operation moving it to the Job configuration screen would make more sense. !upload.png|thumbnail! 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] [cloudbees-folder-plugin] (JENKINS-32586) Move "Delete Job" link to Job configuration screen
Title: Message Title James Dumay created an issue Jenkins / JENKINS-32586 Move "Delete Job" link to Job configuration screen Issue Type: Improvement Assignee: Jesse Glick Attachments: upload.png Components: cloudbees-folder-plugin Created: 25/Jan/16 3:11 AM Priority: Minor Reporter: James Dumay Users have given us feedback that the Delete Job link is a bit too close to the Build Now link. As deleting a Job is not a common operation moving it to the Job configuration screen would make more sense. Add Comment
[JIRA] [cloudbees-folder-plugin] (JENKINS-32585) Deleting a folder should not be shown in the 'actions' menu on the left, but instead should be part of the folder config
Title: Message Title gus reiber created an issue Jenkins / JENKINS-32585 Deleting a folder should not be shown in the 'actions' menu on the left, but instead should be part of the folder config Issue Type: Improvement Assignee: Jesse Glick Components: cloudbees-folder-plugin Created: 25/Jan/16 3:11 AM Priority: Minor Reporter: gus reiber Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [pitmutation-plugin] (JENKINS-31779) javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report
Title: Message Title Edward Kimber commented on JENKINS-31779 Re: javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report Leroy Kendall Thanks very much for the fix!! I have put your changes in a new release which should show up in the update center soon. 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] [ec2-plugin] (JENKINS-32584) ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap
Title: Message Title Francis Upton updated an issue Jenkins / JENKINS-32584 ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap Change By: Francis Upton Priority: Major Critical 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] [ec2-plugin] (JENKINS-32584) ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap
Title: Message Title Francis Upton commented on JENKINS-32584 Re: ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap I think I have fixed this issue. Can you please try installing this to verify the fix: https://jenkins.ci.cloudbees.com/job/plugins/job/ec2-plugin/371/org.jenkins-ci.plugins$ec2/ Once you verify it fixes the issue, I will make a new release. 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] [ec2-plugin] (JENKINS-23678) The documented policy is incomplete
Title: Message Title Francis Upton closed an issue as Fixed This has been fixed on the wiki under the IAM setup Jenkins / JENKINS-23678 The documented policy is incomplete Change By: Francis Upton Status: Open Closed Resolution: Fixed 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] [ec2-plugin] (JENKINS-32584) ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32584 Re: ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap Code changed in jenkins User: Francis Upton IV Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java http://jenkins-ci.org/commit/ec2-plugin/f95e3d52c3872f0fddb1d97f23253b5593eeb641 Log: JENKINS-32584 ec2-plugin counts every instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap 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] [ec2-plugin] (JENKINS-32584) ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap
Title: Message Title Francis Upton started work on JENKINS-32584 Change By: Francis Upton Status: Open In Progress 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] [pitmutation-plugin] (JENKINS-31779) javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31779 Re: javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report Code changed in jenkins User: Ed Kimber Path: src/main/java/org/jenkinsci/plugins/pitmutation/PitProjectAction.java http://jenkins-ci.org/commit/pitmutation-plugin/aa2a09a00c8854fc08e9af819500c5fc9beb58f3 Log: JENKINS-31779 Fix by Leroy Kendall 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] [ansicolor-plugin] (JENKINS-31029) no known implementation of class jenkins.tasks.SimpleBuildWrapper
Title: Message Title davidkarlsen assigned an issue to davidkarlsen Jenkins / JENKINS-31029 no known implementation of class jenkins.tasks.SimpleBuildWrapper Change By: davidkarlsen Assignee: Daniel Doubrovkine davidkarlsen 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] [parameterized-trigger-plugin] (JENKINS-32583) Predefined parameters do not expand variables properly
Title: Message Title
vlad morav updated an issue
Jenkins / JENKINS-32583
Predefined parameters do not expand variables properly
Change By:
vlad morav
When chaining multiple jobs by using the option "Trigger/call builds on other projects", expanding variables in field "Predefined parameters" does not work properly.Example where the first variable gets not expanded in any of the forms below:step_number=$TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME---returns "$TRIGGERED_BUILD_NUMBER_correct_job_name"step_number=${TRIGGERED_BUILD_NUMBER_${LAST_TRIGGERED_JOB_NAME}}---returns "${TRIGGERED_BUILD_NUMBER_correct_job_name}"step_number=${TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME}---returns the same as the second one Maybe it It would be practical to provide the value for TRIGGERED_BUILD_NUMBER with implicit last project name , or add new variable like LAST_BUILD_NUMBER that would provide it .Thanks.
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] [ec2-plugin] (JENKINS-32584) ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap
Title: Message Title Michael Barrientos created an issue Jenkins / JENKINS-32584 ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 24/Jan/16 10:18 PM Priority: Major Reporter: Michael Barrientos Upgraded to just released ec2-plugin 1.30. Have no Jenkins slave running. Trying to get it to auto-create a new slave by running a job. Get this repeatedly in my jenkins log: ``` Jan 24, 2016 2:00:52 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveIfPossible Cannot provision - no capacity for instances: -177 Jan 24, 2016 2:00:52 PM INFO hudson.plugins.ec2.EC2Cloud provision Attempting provision - finished, excess workload: 1 Jan 24, 2016 2:00:59 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveIfPossible Cannot provision - no capacity for instances: -177 Jan 24, 2016 2:00:59 PM INFO hudson.plugins.ec2.EC2Cloud provision Attempting provision - finished, excess workload: 1 ``` In our EC2 region, at the moment we have no Jenkins slaves running, neither on-demand nor spot. There are about 183 instances running or stopped. I think it's counting every single instance, and counting them all against the max slave. This happens regardless of whether I have jenkins configured to create on demand slave or spot slaves. Have to downgrade to get it to autocreate slaves.
[JIRA] [parameterized-trigger-plugin] (JENKINS-32583) Predefined parameters do not expand variables properly
Title: Message Title
vlad morav updated an issue
Jenkins / JENKINS-32583
Predefined parameters do not expand variables properly
Change By:
vlad morav
When chaining multiple jobs by using the option "Trigger/call builds on other projects", expanding variables in field "Predefined parameters" does not work properly.Example where the first variable gets not expanded in any of the forms below:step_number=$TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME---returns "$TRIGGERED_BUILD_NUMBER_correct_job_name"step_number=${TRIGGERED_BUILD_NUMBER_${LAST_TRIGGERED_JOB_NAME}}---returns "${TRIGGERED_BUILD_NUMBER_correct_job_name}"step_number=${TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME}---returns the same as the second oneMaybe it would be enough practical to provide the value for TRIGGERED_BUILD_NUMBER w with implicit last project name.Thanks.
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] [parameterized-trigger-plugin] (JENKINS-32583) Predefined parameters do not expand variables properly
Title: Message Title
vlad morav updated an issue
Jenkins / JENKINS-32583
Predefined parameters do not expand variables properly
Change By:
vlad morav
When chaining multiple jobs by using the option "Trigger/call builds on other projects", expanding variables in field "Predefined parameters" does not work properly.Example where the first variable gets not expanded in any of the forms below:step_number=$TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME---returns "$TRIGGERED_BUILD_NUMBER_correct_job_name"step_number=${TRIGGERED_BUILD_NUMBER_${LAST_TRIGGERED_JOB_NAME}}---returns "${TRIGGERED_BUILD_NUMBER_correct_job_name}"step_number=${TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME}---returns the same as the second one Is this intentional? Maybe would be enough to provide the value for TRIGGERED_BUILD_NUMBER w
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] [parameterized-trigger-plugin] (JENKINS-32583) Predefined parameters do not expand variables properly
Title: Message Title vlad morav started work on JENKINS-32583 Change By: vlad morav Status: Open In Progress 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] [parameterized-trigger-plugin] (JENKINS-32583) Predefined parameters do not expand variables properly
Title: Message Title
vlad morav updated an issue
Jenkins / JENKINS-32583
Predefined parameters do not expand variables properly
Change By:
vlad morav
When chaining multiple jobs and by using the option "Trigger/call builds on other projects", expanding variables in field "Predefined parameters" does not work properly.Example where the first variable gets not expanded in any of the forms below:step_number=$TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME---returns "$TRIGGERED_BUILD_NUMBER_correct_job_name"step_number=${TRIGGERED_BUILD_NUMBER_${LAST_TRIGGERED_JOB_NAME}}---returns "${TRIGGERED_BUILD_NUMBER_correct_job_name}"step_number=${TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME}---returns the same as the second oneIs this intentional?
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] [parameterized-trigger-plugin] (JENKINS-32583) Predefined parameters do not expand variables properly
Title: Message Title vlad morav updated an issue Jenkins / JENKINS-32583 Predefined parameters do not expand variables properly Change By: vlad morav Summary: Predefined parameters does do not expand variables properly 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] [parameterized-trigger-plugin] (JENKINS-32583) Predefined parameters does not expand
Title: Message Title vlad morav updated an issue Jenkins / JENKINS-32583 Predefined parameters does not expand Change By: vlad morav Environment: Jenkins ver. 1.645, plugin version: "2.30", os opensuse/linux 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] [parameterized-trigger-plugin] (JENKINS-32583) Predefined parameters does not expand
Title: Message Title
vlad morav updated an issue
Jenkins / JENKINS-32583
Predefined parameters does not expand
Change By:
vlad morav
When chaining multiple jobs and using the option "Trigger/call builds on other projects", expanding variables in field "Predefined parameters" does not work properly.Example where the first variable gets not expanded in any of the forms below:step_number=$TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME- -- returns "$TRIGGERED_BUILD_NUMBER_correct_job_name"step_number=${TRIGGERED_BUILD_NUMBER_${LAST_TRIGGERED_JOB_NAME}}- -- returns "${TRIGGERED_BUILD_NUMBER_correct_job_name}"step_number=${TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME}- -- returns the same as the second oneIs this intentional?
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] [pitmutation-plugin] (JENKINS-31779) javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report
Title: Message Title Firoz Khan assigned an issue to Edward Kimber Jenkins / JENKINS-31779 javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report Change By: Firoz Khan Assignee: Edward Kimber 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] [parameterized-trigger-plugin] (JENKINS-32583) Predefined parameters does not expand
Title: Message Title
vlad morav updated an issue
Jenkins / JENKINS-32583
Predefined parameters does not expand
Change By:
vlad morav
When chaining multiple jobs and using the option "Trigger/call builds on other projects", expanding variables in field "Predefined parameters" does not work properly.Example where the first variable gets not expanded in any of the forms below:step_number=$TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME # - returns "$TRIGGERED_BUILD_NUMBER_correct_job_name" step_number=${TRIGGERED_BUILD_NUMBER_${LAST_TRIGGERED_JOB_NAME}} # - returns "${TRIGGERED_BUILD_NUMBER_correct_job_name}" step_number=${TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME} # - returns the same as the second oneIs this intentional?
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] [parameterized-trigger-plugin] (JENKINS-32583) Predefined parameters does not expand
Title: Message Title
vlad morav updated an issue
Jenkins / JENKINS-32583
Predefined parameters does not expand
Change By:
vlad morav
When chaining multiple jobs and using the option "Trigger/call builds on other projects", expanding variables in field "Predefined parameters" does not work properly.Example where the variables get first variable gets not expanded in any of the forms below , they are returned as strings exactly as they are typed below :step_number=$TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME # returns "$TRIGGERED_BUILD_NUMBER_correct_job_name" step_number=${TRIGGERED_BUILD_NUMBER_${LAST_TRIGGERED_JOB_NAME}} # returns "${TRIGGERED_BUILD_NUMBER_correct_job_name}" step_number=${TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME} # returns the same as the second one Is this intentional?
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] [pitmutation-plugin] (JENKINS-31779) javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report
Title: Message Title Firoz Khan commented on JENKINS-31779 Re: javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report Great to see fix, Thank you Leroy Kendall . All these days as alternative I have configured HTML report to show up PIT results in CI. 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] [parameterized-trigger-plugin] (JENKINS-32583) Predefined parameters does not expand
Title: Message Title
vlad morav updated an issue
Jenkins / JENKINS-32583
Predefined parameters does not expand
Change By:
vlad morav
When chaining multiple jobs and using the option "Trigger/call builds on other projects", expanding variables in field "Predefined parameters" does not work properly.Example where the variables get not expanded in any form of the forms below, they are returned as strings exactly as they are typed below :step_number=$TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAMEstep_number=${TRIGGERED_BUILD_NUMBER_${LAST_TRIGGERED_JOB_NAME}}step_number=${TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME}Is this intentional?
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] [parameterized-trigger-plugin] (JENKINS-32583) Predefined parameters does not expand
Title: Message Title
vlad morav created an issue
Jenkins / JENKINS-32583
Predefined parameters does not expand
Issue Type:
Bug
Assignee:
huybrechts
Components:
parameterized-trigger-plugin
Created:
24/Jan/16 7:36 PM
Environment:
Jenkins ver. 1.645, opensuse/linux
Priority:
Major
Reporter:
vlad morav
When chaining multiple jobs and using the option "Trigger/call builds on other projects", expanding variables in field "Predefined parameters" does not work properly.
Example where the variables get not expanded in any form:
step_number=$TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME step_number=${TRIGGERED_BUILD_NUMBER_${LAST_TRIGGERED_JOB_NAME}} step_number=$ {TRIGGERED_BUILD_NUMBER_$LAST_TRIGGERED_JOB_NAME}
Is this intentional?
[JIRA] [ws-cleanup-plugin] (JENKINS-22696) Delete workspace with sudo doesn't work
Title: Message Title St. John Johnson commented on JENKINS-22696 Re: Delete workspace with sudo doesn't work Did you ever check if requireTTY was set? That could cause the failure. 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] [pitmutation-plugin] (JENKINS-31779) javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report
Title: Message Title
Leroy Kendall edited a comment on JENKINS-31779
Re: javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report
I was able to fix this. Here is the diff: {code:java} src/main/java/org/jenkinsci/plugins/pitmutation/PitProjectAction.java index e7a76b4..73a7b7c 100644@@ -15,12 +15,16 @@ public class PitProjectAction extends Actionable implements ProminentProjectActi public PitProjectAction(AbstractProject project) { this.project = project; -PitPublisher cp = (PitPublisher) project.getPublishersList().get(PitPublisher.DESCRIPTOR);+//PitPublisher cp = (PitPublisher) project.getPublishersList().get(PitPublisher.DESCRIPTOR); //if (cp != null) { // onlyStable = cp.getOnlyStable(); //} } + public AbstractProject getProject() {+return project;+ }+ /*** Getter for property 'lastResult'.* {code}
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] [pitmutation-plugin] (JENKINS-31779) javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report
Title: Message Title
Leroy Kendall commented on JENKINS-31779
Re: javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report
I was able to fix this. Here is the diff:
src/main/java/org/jenkinsci/plugins/pitmutation/PitProjectAction.java index e7a76b4..73a7b7c 100644 @@ -15,12 +15,16 @@ public class PitProjectAction extends Actionable implements ProminentProjectActi public PitProjectAction(AbstractProject project) { this.project = project;
PitPublisher cp = (PitPublisher) project.getPublishersList().get(PitPublisher.DESCRIPTOR); +// PitPublisher cp = (PitPublisher) project.getPublishersList().get(PitPublisher.DESCRIPTOR); // if (cp != null) { // _onlyStable_ = cp.getOnlyStable(); // }
}
+ public AbstractProject getProject() { + return project; + }
+ /**
Getter for property 'lastResult'. *
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] [terraform-plugin] (JENKINS-32306) Could not call hudson.FilePath.writeObject()
Title: Message Title Arul Jegadish commented on JENKINS-32306 Re: Could not call hudson.FilePath.writeObject() +1. I'm facing the same issue when the Job is configured to run on a slave. 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] [github-plugin] (JENKINS-24690) Report failures to attach hook in UI
Title: Message Title Kirill Merkushev commented on JENKINS-24690 Re: Report failures to attach hook in UI Implementation: https://github.com/jenkinsci/github-plugin/pull/106 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] [github-plugin] (JENKINS-24690) Report failures to attach hook in UI
Title: Message Title Kirill Merkushev stopped work on JENKINS-24690 Change By: Kirill Merkushev Status: In Progress Open 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] [An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Inv
Title: Message Title Daniel Beck deleted an issue test / TEST-85 How to grow your health by hub 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] [subversion-plugin] (JENKINS-32582) List Subversion Tags default tag fails for Poll SCM trigger
Title: Message Title Glenn Widener created an issue Jenkins / JENKINS-32582 List Subversion Tags default tag fails for Poll SCM trigger Issue Type: Bug Assignee: Unassigned Attachments: Untitled.png Components: subversion-plugin Created: 24/Jan/16 5:42 PM Environment: svn plugin v2.5.7 or 2.5.3, Jenkins 1.643, ubuntu 14, jre 1.7.0_91-b02 Priority: Major Reporter: Glenn Widener The List Subversion Tags default tag (e.g. "trunk") is not obeyed for Poll SCM trigger. Instead, the most recent tag from a manual build is used. This makes it unusable for the most natural use case: nightly triggered trunk rebuilds plus manual branch builds. Best workaround is terrible: trigger a rebuild on Success, with parameters to override tag: fail=t svn_tag=trunk Build script aborts with failure if fail=t, stopping the infinite build loop, but always leaving the job in a failed state. Ugh.
[JIRA] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
Title: Message Title Leon Blakey commented on JENKINS-28175 Re: config change deadlock Jenkins when pircx.shutdown() is invoked PircBotX 2.1 was released last night. 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] [test1] (TEST-85) How to grow your health by hub
Title: Message Title bhasker nimi commented on TEST-85 Re: How to grow your health by hub hello... 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] [test1] (TEST-85) How to grow your health by hub
Title: Message Title bhasker nimi updated an issue test / TEST-85 How to grow your health by hub Change By: bhasker nimi Summary: How to grow your health by bhasker hub 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] [test1] (TEST-85) How to grow your health by bhasker
Title: Message Title bhasker nimi updated an issue test / TEST-85 How to grow your health by bhasker Change By: bhasker nimi Summary: How to grow your health by me bhasker 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] [test1] (TEST-85) How to grow your health by me
Title: Message Title bhasker nimi created an issue test / TEST-85 How to grow your health by me Issue Type: Story Assignee: bhasker nimi Components: test1 Created: 24/Jan/16 2:16 PM Environment: Find science-based health information on symptoms, diagnosis, treatments, research, clinical trials and more from NIH, the nation's medical research agency. Labels: user-experience Priority: Major Reporter: bhasker nimi Find science-based health information on symptoms, diagnosis, treatments, research, clinical trials and more from NIH, the nation's medical research agency.
[JIRA] [ws-cleanup-plugin] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Thomas Collignon commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves And I have submit a pull request to add a new option to switch between synch and asynch mode without downgrading : https://github.com/jenkinsci/ws-cleanup-plugin/pull/26 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] [ws-cleanup-plugin] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Thomas Collignon commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves In fact if you want to switch "asynch/synch" mode, you can add Patterns, because this will affect cleanup method : Add Patterns : synch mode No Patterns : asynch mode This is just a trick to see the cleanup problem without downgrade to 0.23. 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] [pitmutation-plugin] (JENKINS-31779) javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report
Title: Message Title Leroy Kendall commented on JENKINS-31779 Re: javax.servlet.ServletException Caused by: org.apache.commons.jelly.JellyTagException: in PIT Mutation Report I have exactly the same issue. Is there any ETA when it is fixed? Does anybody work on this issue? It blocks us from using pit mutation plugin in Jenkins. Thanks. 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] [android-emulator-plugin] (JENKINS-32581) getting device offline occasionally when connecting an emulator
Title: Message Title guy lis created an issue Jenkins / JENKINS-32581 getting device offline occasionally when connecting an emulator Issue Type: Bug Assignee: Christopher Orr Components: android-emulator-plugin Created: 24/Jan/16 10:10 AM Priority: Minor Reporter: guy lis When trying to connect an emulator with version 21, occasionally getting the error 11:58:24 error: device offline 11:58:24 $ /data/kira/Utils/android-sdk-linux//platform-tools/adb connect localhost:44453 11:58:37 $ /data/kira/Utils/android-sdk-linux//platform-tools/adb -s localhost:44453 shell getprop dev.bootcomplete I'm trying with an android plugin version v2.10 as well as the latest one. The problem does not occur with version 17, but my minimu, version is above that. I saw many comments on this issue, but none explained if the issue is resolved Add Comment
[JIRA] [core] (JENKINS-32578) Better config page navigation - phase 2 (and beyond)
Title: Message Title
Tom FENNELLY updated an issue
Jenkins / JENKINS-32578
Better config page navigation - phase 2 (and beyond)
Change By:
Tom FENNELLY
Another iteration of UX improvements to the config pages following on from [JENKINS-32357|https://issues.jenkins-ci.org/browse/JENKINS-32357].h2. Possible target features for "phase 2" (and beyond)# *More _javascript_ unit tests*. In particular around the finder feature.# *Split out config/table-metadata.js*. Refactor [config/table-metadata.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/table-metadata.js] to extract {{ConfigTableMetaData}}, {{ConfigSection}} and {{ConfigRowSet}} into modules of their own. They've outgrown where they are.# *Better {{row-set}} modeling in the _javascript_ API*. Current version was created by "decompiling" the DOM structure and making a best guess. KK has promised to help formalise.# *Section merging*. Visual merging of sections e.g. perhaps the "Advanced Project Options" section should really be moved into the "General" section.# *Section extraction*. Visually extract parts of a section to visually create a new section e.g. visually extract build parameters into a section of their own.# *Finder auto-complete*.# *Try accordion based navigation* (instead of Tabs). See [config/tabbar.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/tabbar.js] and do something similar for accordions.# *Try a "left tree" based navigation* (instead of Tabs). See [config/tabbar.js|https://github.com/tfennelly/jenkins/blob/2.0-with-config-tabs/war/src/main/js/widgets/config/tabbar.js] and do something similar etc. # *New Item Wizards*. Maybe we can create some "New Item" wizards that help users configure new Jobs more easily. E.g. for a freestyle job, something that guides you to configure the SCM and then some Build actions. I think this would be especially useful for new Jenkins users. Of course it needs to be something that can be turned off easily (with a "don't show me this anymore" type checkbox). What else could we do? Please feel free to add ideas in comments and we'll then move them to the list here.
Add Comment
[JIRA] [core] (JENKINS-11771) java.lang.RuntimeException: Failed to instantiate class hudson.triggers.TimerTrigger when adding a space to invalid cron syntax after being warned about invalid input
Title: Message Title boris bondarenko commented on JENKINS-11771 Re: java.lang.RuntimeException: Failed to instantiate class hudson.triggers.TimerTrigger when adding a space to invalid cron syntax after being warned about invalid input also reproducible in Jenkins ver. 1.596.2 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] [core] (JENKINS-32340) Cannot enable disabled dependencies
Title: Message Title
Félix Belzunce Arcos updated an issue
Jenkins / JENKINS-32340
Cannot enable disabled dependencies
Change By:
Félix Belzunce Arcos
URL:
https://github.com/jenkinsci/jenkins/pull/2002
It's not possible to enable disabled dependencies that should not have been disabled in the first place.Steps to reproduce:{noformat}$ export JAVA_HOME=$HOME/DisabledDependencyHome$ java -jar jenkins.war^C$ touch $JENKINS_HOME/plugins / {junit,matrix-project,maven-plugin}.jpi.disabled$ java -jar jenkins.war{noformat}No warnings upon second startup, and JUnit plugin cannot be enabled through the UI
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.
