[JIRA] (JENKINS-13192) groovy template meets error when there are git changes

[ https://issues.jenkins-ci.org/browse/JENKINS-13192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161063#comment-161063 ] SCM/JIRA link daemon commented on JENKINS-13192: Code changed in jenkins Use

[JIRA] (JENKINS-13192) groovy template meets error when there are git changes

[ https://issues.jenkins-ci.org/browse/JENKINS-13192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161062#comment-161062 ] SCM/JIRA link daemon commented on JENKINS-13192: Code changed in jenkins Use

[JIRA] (JENKINS-13192) groovy template meets error when there are git changes

[ https://issues.jenkins-ci.org/browse/JENKINS-13192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161061#comment-161061 ] Larry Cai commented on JENKINS-13192: - Haha, ok, fixed now. See pull request https://gi

[JIRA] (JENKINS-12825) Allow expansion of environment variables in the configuration

[ https://issues.jenkins-ci.org/browse/JENKINS-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161060#comment-161060 ] Zachary Young commented on JENKINS-12825: - I would like to see this also, with varia

[JIRA] (JENKINS-13215) NullPointerException when Category have value : not selected

[ https://issues.jenkins-ci.org/browse/JENKINS-13215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161059#comment-161059 ] dogfood commented on JENKINS-13215: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/

[JIRA] (JENKINS-13215) NullPointerException when Category have value : not selected

[ https://issues.jenkins-ci.org/browse/JENKINS-13215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161058#comment-161058 ] SCM/JIRA link daemon commented on JENKINS-13215: Code changed in jenkins Use

[JIRA] (JENKINS-13215) NullPointerException when Category have value : not selected

[ https://issues.jenkins-ci.org/browse/JENKINS-13215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13215. Resolution: Fixed > NullPointerException when Category have value : n

[JIRA] (JENKINS-11824) Can't use a env parameter for "Stream selector" when recommended baseline is selected (fix attached)

[ https://issues.jenkins-ci.org/browse/JENKINS-11824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161057#comment-161057 ] dogfood commented on JENKINS-11824: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/

[JIRA] (JENKINS-5227) Add an option to override the 'cleartool' location for slaves

[ https://issues.jenkins-ci.org/browse/JENKINS-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Latombe closed JENKINS-5227. > Add an option to override the 'cleartool' location for slaves >

[JIRA] (JENKINS-8497) Ability to use job parameter in all configuration fields (i.e. load rules)

[ https://issues.jenkins-ci.org/browse/JENKINS-8497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Latombe closed JENKINS-8497. > Ability to use job parameter in all configuration fields (i.e. load rules) > ---

[JIRA] (JENKINS-11824) Can't use a env parameter for "Stream selector" when recommended baseline is selected (fix attached)

[ https://issues.jenkins-ci.org/browse/JENKINS-11824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161055#comment-161055 ] SCM/JIRA link daemon commented on JENKINS-11824: Code changed in jenkins Use

[JIRA] (JENKINS-10077) archiving large files takes extrordinarily long time

[ https://issues.jenkins-ci.org/browse/JENKINS-10077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois closed JENKINS-10077. --- Resolution: Won't Fix Unfortunately, I can't fix this issue. If in your context it is slow, I suggest you s

[JIRA] (JENKINS-11867) Deployed files have a different time with original files.

[ https://issues.jenkins-ci.org/browse/JENKINS-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-11867. - Resolution: Fixed Sorry for this late fix. Available in 0.15 > Deployed files have a d

[JIRA] (JENKINS-11867) Deployed files have a different time with original files.

[ https://issues.jenkins-ci.org/browse/JENKINS-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161053#comment-161053 ] SCM/JIRA link daemon commented on JENKINS-11867: Code changed in jenkins Use

[JIRA] (JENKINS-12565) maven 2/3 job automatically archives the artifact(s) but without the "archive artifacts checkbox" and a pattern post build deploy to fails

[ https://issues.jenkins-ci.org/browse/JENKINS-12565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois closed JENKINS-12565. --- Resolution: Won't Fix ArtifactDeployer will not be aware of automatic Maven2 archiving > m

[JIRA] (JENKINS-8682) Disable polling if build is running

[ https://issues.jenkins-ci.org/browse/JENKINS-8682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161051#comment-161051 ] dogfood commented on JENKINS-8682: -- Integrated in !http://ci.jenkins-ci.org/images/16x16/blu

[JIRA] (JENKINS-12522) Deploy artifacts for failed builds, too

[ https://issues.jenkins-ci.org/browse/JENKINS-12522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-12522. - Resolution: Fixed > Deploy artifacts for failed builds, too > -

[JIRA] (JENKINS-7122) Disable lshistory

[ https://issues.jenkins-ci.org/browse/JENKINS-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Latombe closed JENKINS-7122. > Disable lshistory > -- > > Key: JENKINS-7122 >

[JIRA] (JENKINS-9631) ClearCase Plugin: SCM Polling Branch System-Level Config Setting Does Not Work

[ https://issues.jenkins-ci.org/browse/JENKINS-9631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Latombe closed JENKINS-9631. > ClearCase Plugin: SCM Polling Branch System-Level Config Setting Does Not Work > ---

[JIRA] (JENKINS-9630) ClearCase Plugin: SCM Polling Branch System-Level Config Setting Does Not Work

[ https://issues.jenkins-ci.org/browse/JENKINS-9630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Latombe closed JENKINS-9630. > ClearCase Plugin: SCM Polling Branch System-Level Config Setting Does Not Work > ---

[JIRA] (JENKINS-8682) Disable polling if build is running

[ https://issues.jenkins-ci.org/browse/JENKINS-8682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161050#comment-161050 ] SCM/JIRA link daemon commented on JENKINS-8682: --- Code changed in jenkins User:

[JIRA] (JENKINS-12522) Deploy artifacts for failed builds, too

[ https://issues.jenkins-ci.org/browse/JENKINS-12522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161049#comment-161049 ] SCM/JIRA link daemon commented on JENKINS-12522: Code changed in jenkins Use

F ind no com mitme nt aff airs. Larg est casu al en counters si te. No ris k to jo in.

F ind no com mitme nt aff airs. Larg est casu al en counters si te. No ris k to jo in. http://fc.cx/h - If you would like to not be contacted from us in the future please email us at: newburycor [at] gmail [dot] com Or write to: P.O. Box 191, 62 Street, Vancouver

[JIRA] (JENKINS-11375) Provide Clearcase changed files to email-ext standard HTML jelly template

[ https://issues.jenkins-ci.org/browse/JENKINS-11375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161048#comment-161048 ] SCM/JIRA link daemon commented on JENKINS-11375: Code changed in jenkins Use

[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue

[ https://issues.jenkins-ci.org/browse/JENKINS-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-12994. --- Resolution: Fixed > Quiet period is blocking other jobs in queue >

[JIRA] (JENKINS-12042) SVN_REVISION varable is empty if URL contains "@Revision"

[ https://issues.jenkins-ci.org/browse/JENKINS-12042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161047#comment-161047 ] OHTAKE Tomohiro commented on JENKINS-12042: --- The issue has been fixed in 1.32. (JE

[JIRA] (JENKINS-13242) Email Extension plugin - groovy and jelly do not update $rooturl after Jenkins URL updated

[ https://issues.jenkins-ci.org/browse/JENKINS-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shinsato resolved JENKINS-13242. Fix Version/s: current Resolution: Fixed This will be released with 2.20.

[JIRA] (JENKINS-13242) Email Extension plugin - groovy and jelly do not update $rooturl after Jenkins URL updated

[ https://issues.jenkins-ci.org/browse/JENKINS-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shinsato reassigned JENKINS-13242: -- Assignee: shinsato > Email Extension plugin - groovy and jelly do not update $rooturl aft

[JIRA] (JENKINS-13298) Update JNA from version 3.3 to 3.4

Cory Downey created JENKINS-13298: -- Summary: Update JNA from version 3.3 to 3.4 Key: JENKINS-13298 URL: https://issues.jenkins-ci.org/browse/JENKINS-13298 Project: Jenkins Issue Type: Impro

[JIRA] (JENKINS-13221) The integration does not examine the filesystem to see if files in the workspace is missing.

[ https://issues.jenkins-ci.org/browse/JENKINS-13221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161045#comment-161045 ] Cletus D'Souza commented on JENKINS-13221: -- Seems like a reasonable request for pro

[JIRA] (JENKINS-13220) The integration inconsistently handles change packages that are submitted but not yet accepted.

[ https://issues.jenkins-ci.org/browse/JENKINS-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161044#comment-161044 ] Cletus D'Souza commented on JENKINS-13220: -- If the new files are showing up in the

[JIRA] (JENKINS-13238) Loading All Build History Fails

[ https://issues.jenkins-ci.org/browse/JENKINS-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161043#comment-161043 ] dogfood commented on JENKINS-13238: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/

[JIRA] (JENKINS-13136) Environment Variable Injection injecting (and overriding) unwanted variables (ie JAVA_HOME)

[ https://issues.jenkins-ci.org/browse/JENKINS-13136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161042#comment-161042 ] Alex Gray commented on JENKINS-13136: - Unfortunately no, except the problem is still the

[JIRA] (JENKINS-9965) Nunit plugin does not display graph when fingerprinting is used on the xml report

[ https://issues.jenkins-ci.org/browse/JENKINS-9965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161041#comment-161041 ] steven armstrong commented on JENKINS-9965: --- is there any update on this has it bee

[JIRA] (JENKINS-13043) Test Results Trend graph missing intermittently

[ https://issues.jenkins-ci.org/browse/JENKINS-13043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161040#comment-161040 ] steven armstrong commented on JENKINS-13043: This is a big problem for us as we

[JIRA] (JENKINS-13238) Loading All Build History Fails

[ https://issues.jenkins-ci.org/browse/JENKINS-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161039#comment-161039 ] SCM/JIRA link daemon commented on JENKINS-13238: Code changed in jenkins Use

[JIRA] (JENKINS-13238) Loading All Build History Fails

[ https://issues.jenkins-ci.org/browse/JENKINS-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13238. Resolution: Fixed > Loading All Build History Fails > ---

[JIRA] (JENKINS-13238) Loading All Build History Fails

[ https://issues.jenkins-ci.org/browse/JENKINS-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sogabe reassigned JENKINS-13238: Assignee: sogabe > Loading All Build History Fails > --- > >

[JIRA] (JENKINS-13289) Make 'Advanced' button collapsible

[ https://issues.jenkins-ci.org/browse/JENKINS-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161038#comment-161038 ] domi commented on JENKINS-13289: looks great! > Make 'Advanced' button coll

[JIRA] (JENKINS-12250) Critical block can not be added into conditional step

[ https://issues.jenkins-ci.org/browse/JENKINS-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161037#comment-161037 ] domi commented on JENKINS-12250: it looks like you have not successfully installed the new v

[JIRA] (JENKINS-13112) Adding any post-build step as a build step causes exception

[ https://issues.jenkins-ci.org/browse/JENKINS-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161036#comment-161036 ] domi edited comment on JENKINS-13112 at 3/31/12 9:30 AM: - I think I

[JIRA] (JENKINS-13112) Adding any post-build step as a build step causes exception

[ https://issues.jenkins-ci.org/browse/JENKINS-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161036#comment-161036 ] domi commented on JENKINS-13112: I think I finally figured you'r usecase - it it does not wo

[JIRA] (JENKINS-13112) Adding any post-build step as a build step causes exception

[ https://issues.jenkins-ci.org/browse/JENKINS-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13112. Resolution: Fixed > Adding any post-build step as a build step causes

[JIRA] (JENKINS-13112) Adding any post-build step as a build step causes exception

[ https://issues.jenkins-ci.org/browse/JENKINS-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161035#comment-161035 ] SCM/JIRA link daemon commented on JENKINS-13112: Code changed in jenkins Use

[JIRA] (JENKINS-13268) Build hang

[ https://issues.jenkins-ci.org/browse/JENKINS-13268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois updated JENKINS-13268: Component/s: core (was: buildresult-trigger) > Build hang > -- > >

[JIRA] (JENKINS-13204) Add "Poll Now" Feature

[ https://issues.jenkins-ci.org/browse/JENKINS-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois closed JENKINS-13204. --- Resolution: Postponed Thank you so much for your inputs. I'm choosing to postpone the issue resolution due

[JIRA] (JENKINS-13293) Add cron syntax to set Time Zone

[ https://issues.jenkins-ci.org/browse/JENKINS-13293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois updated JENKINS-13293: Component/s: core (was: buildresult-trigger) buildresult-trigger plugin delegates it

[JIRA] (JENKINS-13136) Environment Variable Injection injecting (and overriding) unwanted variables (ie JAVA_HOME)

[ https://issues.jenkins-ci.org/browse/JENKINS-13136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161032#comment-161032 ] gbois edited comment on JENKINS-13136 at 3/31/12 8:57 AM: -- Do you h

[JIRA] (JENKINS-13136) Environment Variable Injection injecting (and overriding) unwanted variables (ie JAVA_HOME)

[ https://issues.jenkins-ci.org/browse/JENKINS-13136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161032#comment-161032 ] gbois edited comment on JENKINS-13136 at 3/31/12 8:57 AM: -- Do you h

[JIRA] (JENKINS-13136) Environment Variable Injection injecting (and overriding) unwanted variables (ie JAVA_HOME)

[ https://issues.jenkins-ci.org/browse/JENKINS-13136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161032#comment-161032 ] gbois commented on JENKINS-13136: - Do you any new information? > Environmen

[JIRA] (JENKINS-13112) Adding any post-build step as a build step causes exception

[ https://issues.jenkins-ci.org/browse/JENKINS-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161031#comment-161031 ] domi commented on JENKINS-13112: Anthony, I'm looking into the code and I'm still stuck, the

[JIRA] (JENKINS-13297) Make order of main sections the same between 'FreesytleJob' and 'Maven Job'

[ https://issues.jenkins-ci.org/browse/JENKINS-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161030#comment-161030 ] dogfood commented on JENKINS-13297: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/

[JIRA] (JENKINS-13297) Make order of main sections the same between 'FreesytleJob' and 'Maven Job'

[ https://issues.jenkins-ci.org/browse/JENKINS-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13297. Resolution: Fixed > Make order of main sections the same between 'Fre

[JIRA] (JENKINS-13297) Make order of main sections the same between 'FreesytleJob' and 'Maven Job'

[ https://issues.jenkins-ci.org/browse/JENKINS-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161029#comment-161029 ] SCM/JIRA link daemon commented on JENKINS-13297: Code changed in jenkins Use

[JIRA] (JENKINS-13297) Make order of main sections the same between 'FreesytleJob' and 'Maven Job'

domi created JENKINS-13297: -- Summary: Make order of main sections the same between 'FreesytleJob' and 'Maven Job' Key: JENKINS-13297 URL: https://issues.jenkins-ci.org/browse/JENKINS-13297 Project: Jenkins

[JIRA] (JENKINS-13263) Downstream jobs inherit same changeset

[ https://issues.jenkins-ci.org/browse/JENKINS-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Petti resolved JENKINS-13263. - Assignee: Rob Petti (was: Carl Quinn) Resolution: Fixed This information can now be obta

[JIRA] (JENKINS-13263) Downstream jobs inherit same changeset

[ https://issues.jenkins-ci.org/browse/JENKINS-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Petti updated JENKINS-13263: Component/s: display-upstream-changes (was: perforce) > Downstream jobs

[JIRA] (JENKINS-13296) Changelists that include excluded files and files outside of the client view will trigger a build.

[ https://issues.jenkins-ci.org/browse/JENKINS-13296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Petti reassigned JENKINS-13296: --- Assignee: Rob Petti > Changelists that include excluded files and files outside of the

[JIRA] (JENKINS-13296) Changelists that include excluded files and files outside of the client view will trigger a build.

[ https://issues.jenkins-ci.org/browse/JENKINS-13296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161027#comment-161027 ] Rob Petti commented on JENKINS-13296: - Yeah, you've definitely found a bug, and a tricky