[JIRA] (JENKINS-36437) Mock support
Title: Message Title Jo Shields updated an issue Jenkins / JENKINS-36437 Mock support Okay, I have initial support working on a branch: https://github.com/directhex/chroot-plugin/tree/mock-support I can't make a PR until https://github.com/jenkinsci/chroot-plugin/pull/8 is merged, as it's based on some common code. Issues: Requires passwordless sudo on `/bin/tar` and `/bin/rm`. You should consider this pretty much equivalent to "the whole thing is horribly insecure" Not everything is plugged in and working yet - just basic script execution and package building Available chroots are defined entirely by your installed Mock version, no support for overriding the contents of /etc/mock Scripts execute silently (this is a design issue with Mock, verbose mode doesn't change it). Packages are noisy (intentionally verbose) An example build with my branch: https://jenkins.mono-project.com/view/Releases/job/nightly-stablerpm-stablepkg/78/label=epel-7-x86_64/consoleFull Change By: Jo Shields Summary: Mock support structural issues Add Comment
[JIRA] (JENKINS-36437) Mock support structural issues
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-36437 Mock support structural issues Issue Type: New Feature Assignee: Unassigned Components: chroot-plugin Created: 2016/Jul/05 11:30 AM Priority: Minor Reporter: Jo Shields I'm looking at finishing the Mock back-end enough to make it work. Implementing healthCheck() is enough for the chroot init to actually start working. However, this reveals a bigger issue - the lowest common functional unit for chroot-plugin is a tarball (since it's modelled on pbuilder, which uses self-contained tarballs). However, Mock doesn 't use or produce tarballs, it produces directory structures. I'm not certain whether it's better to wrap up Mock's output in tar, or alter chroot-plugin to operate on directories at a time - my suspicion is the former is the better route, as a sudo exception for tar is less bad than the security hell of trying to copy entire root filesystems full of device nodes around. Both issues might be mitigated if the chroot could be initialised in its final destination directly, i.e. avoid the create-generic-chroot-and-copy-to-job workflow for mock. Add Comment
[JIRA] (JENKINS-33519) Job execution fails if "Clear" enabled & chroot does not exist yet
Title: Message Title Jo Shields closed an issue as Fixed Jenkins / JENKINS-33519 Job execution fails if "Clear" enabled & chroot does not exist yet Change By: Jo Shields Status: Open Closed Resolution: Fixed 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-33521) Use textbox for chroot name, and allow environment expansion
Title: Message Title Jo Shields resolved as Fixed Jenkins / JENKINS-33521 Use textbox for chroot name, and allow environment expansion Change By: Jo Shields Status: Open Resolved Resolution: Fixed 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] [s3-plugin] (JENKINS-35123) Matrix project support removed
Title: Message Title
Jo Shields updated an issue
Jenkins / JENKINS-35123
Matrix project support removed
Change By:
Jo Shields
commit 0b4db3ac730702791a67dccbc881a0582cebecb1 removed previously functional support for matrix jobs.Old behaviour:{{Copied 4 artifacts from "Build Mono .deb » debian-amd64" build number 2578 stored in S3 }} {{ Copied 2 artifacts from "Build Mono .deb » debian-armel" build number 2578 stored in S3 }} {{ Copied 2 artifacts from "Build Mono .deb » debian-armhf" build number 2578 stored in S3 }} {{ Copied 2 artifacts from "Build Mono .deb » debian-i386" build number 2578 stored in S3}}New behaviour:{{Build #2616[2616] doesn't have any S3 artifacts uploaded}}
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] [s3-plugin] (JENKINS-35123) Matrix project support removed
Title: Message Title
Jo Shields created an issue
Jenkins / JENKINS-35123
Matrix project support removed
Issue Type:
Bug
Assignee:
Alexander A
Components:
s3-plugin
Created:
2016/May/25 11:48 AM
Priority:
Minor
Reporter:
Jo Shields
commit 0b4db3ac730702791a67dccbc881a0582cebecb1 removed previously functional support for matrix jobs.
Old behaviour:
{{Copied 4 artifacts from "Build Mono .deb » debian-amd64" build number 2578 stored in S3 Copied 2 artifacts from "Build Mono .deb » debian-armel" build number 2578 stored in S3 Copied 2 artifacts from "Build Mono .deb » debian-armhf" build number 2578 stored in S3 Copied 2 artifacts from "Build Mono .deb » debian-i386" build number 2578 stored in S3}}
New behaviour:
Build #2616[2616] doesn't have any S3 artifacts uploaded
Add Comment
[JIRA] [chroot-plugin] (JENKINS-34978) Please stop swallowing exceptions and debug output
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-34978 Please stop swallowing exceptions and debug output Issue Type: Improvement Assignee: Unassigned Components: chroot-plugin Created: 2016/May/20 10:24 AM Priority: Minor Reporter: Jo Shields It can take a few tries to get the chroot plugin working properly, but when it fails, it is entirely opaque as to why. Nothing gets logged to the Jenkins log - exceptions aren't shown, STDERR from pbuilder isn't available, etc. It can make it super difficult to work out the cause of problems, especially when it happens in production but not the test environment your debugger is attached to. Add Comment
[JIRA] [core] (JENKINS-34768) Smarter worker selection needed
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-34768 Smarter worker selection needed Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/May/12 2:42 PM Priority: Minor Reporter: Jo Shields I have six machines, 2 executors each, capable of running 32-bit ARM jobs (i.e. have labels identifying as such) I have five machines, 3 executors each, capable of running either 32-bit or 64-bit ARM jobs (i.e. have labels identifying as such Which means a total of 27 executor slots for label debian-8-armel and 15 for debian-8-arm64 Jenkins needs to consider the number of labels serviced by a slot, and prioritise more scarce resources - right now I have 4 queued jobs which want debian-8-arm64 machines, but they're 100% full running debian-8-armel jobs. Meanwhile I have empty debian-8-armel executors on the 32-bit machines. That's dumb and it should be less dumb. Add Comment
[JIRA] [xunit-plugin] (JENKINS-14117) The plugin hasn't been performed correctly: remote file operation failed
Title: Message Title Jo Shields commented on JENKINS-14117 Re: The plugin hasn't been performed correctly: remote file operation failed Same here: https://jenkins-master-2.cloudapp.net/job/test-monodevelop-mainline/label=ubuntu-1404-amd64/3146/console I can definitely see that file exists at that path & contains data. 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] [workflow-plugin] (JENKINS-26522) Annotated block/stage status
Title: Message Title
Jo Shields edited a comment on JENKINS-26522
Re: Annotated block/stage status
Okay, to try & better explain what we're trying to achieve, here's our current implementation, which is split into three parts:h2. Custom logic in the job shell script to annotate resultsroughly speaking, this looks like:{{STEP="System.Security-4.5"}}{{STARTTIME=`date +%s`}}{{echo "*** start: $\{STEP\}"}}{{$\{TIMEOUTCMD\} --signal=ABRT --kill-after=60s 5m make -w -C mcs/class/System.Security run-test TEST_HARNESS_FLAGS=-labels PROFILE=""> \ (date +%s \ ) - $\{STARTTIME\} | bc \ ) \ ): ${STEP}: \\e[42mPassed\e[0m" || echo -e "*** end($(echo $ \ (date +%s \ ) - $\{STARTTIME\} | bc \ ) \ ): ${STEP}: \\e[43mUnstable\e[0m"}}This assigns blocks of tests (roughly equivalent to Pipeline stages) to run together, with a common timeout, and either a "pass" status or an "unstable" status (unstable indicating this block had a non-zero exit status, but that execution of the script should continue). For steps where failure should be deemed critical, the colour code is red instead of yellow, status text says "failed", and there's some extra {{exit 1}}'s thrown in.h2, Groovy script to parse the build log and generate a job status tablePretty much just builds an HTML , pairing "*** start" and "*** end" lines to build the table structure and write the execution time, and adding the most recent test runner output as an at-a-glance summaryh2, Aggregate the data from multiple jobs in a giant table, with a custom pluginthis gives the most dense data view we can manage - 76 steps, 5 architectures, with an at-a-glance look for developers of "did I break tests grouped into X on architecture Y", or "is builder Z misbehaving and in need of attention"I would love to move as much of this crap into a Jenkinsfile as possible. Certainly parts 1 and 2 of the above seem theoretically feasible to me, but there are gaps that means I'd just end up emulating bash _really badly_ in Groovy, rather than taking advantage of Pipeline features (because the Pipeline versions are missing things)
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
[JIRA] [workflow-plugin] (JENKINS-26522) Annotated block/stage status
Title: Message Title
Jo Shields edited a comment on JENKINS-26522
Re: Annotated block/stage status
Okay, to try & better explain what we're trying to achieve, here's our current implementation, which is split into three parts:h2. Custom logic in the job shell script to annotate resultsroughly speaking, this looks like:{{STEP="System.Security-4.5"}}{{STARTTIME=`date +%s`}}{{echo "*** start: $\{STEP\}"}}{{$\{TIMEOUTCMD\} --signal=ABRT --kill-after=60s 5m make -w -C mcs/class/System.Security run-test TEST_HARNESS_FLAGS=-labels PROFILE="" />This assigns blocks of tests (roughly equivalent to Pipeline stages) to run together, with a common timeout, and either a "pass" status or an "unstable" status (unstable indicating this block had a non-zero exit status, but that execution of the script should continue). For steps where failure should be deemed critical, the colour code is red instead of yellow, status text says "failed", and there's some extra {{exit 1}}'s thrown in.h2 , . Groovy script to parse the build log and generate a job status tablePretty much just builds an HTML , pairing "*** start" and "*** end" lines to build the table structure and write the execution time, and adding the most recent test runner output as an at-a-glance summaryh2 , . Aggregate the data from multiple jobs in a giant table, with a custom pluginthis gives the most dense data view we can manage - 76 steps, 5 architectures, with an at-a-glance look for developers of "did I break tests grouped into X on architecture Y", or "is builder Z misbehaving and in need of attention"I would love to move as much of this crap into a Jenkinsfile as possible. Certainly parts 1 and 2 of the above seem theoretically feasible to me, but there are gaps that means I'd just end up emulating bash _really badly_ in Groovy, rather than taking advantage of Pipeline features (because the Pipeline versions are missing things)
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 mor
[JIRA] [workflow-plugin] (JENKINS-26522) Annotated block/stage status
Title: Message Title
Jo Shields edited a comment on JENKINS-26522
Re: Annotated block/stage status
Okay, to try & better explain what we're trying to achieve, here's our current implementation, which is split into three parts:h2. Custom logic in the job shell script to annotate resultsroughly speaking, this looks like:{{STEP="System.Security-4.5"}}{{STARTTIME=`date +%s`}}{{echo "*** start: $\{STEP\}"}}{{$\{TIMEOUTCMD\} --signal=ABRT --kill-after=60s 5m make -w -C mcs/class/System.Security run-test TEST_HARNESS_FLAGS=-labels PROFILE=""> \ ($ \ (echo $\(date +%s\) - $\{STARTTIME\} | bc\)\): $ \ {STEP \ }: \\e[42mPassed\e[0m" || echo -e "*** end \ ($ \ (echo $\(date +%s\) - $\{STARTTIME\} | bc\)\): $ \ {STEP \ }: \\e[43mUnstable\e[0m"}}This assigns blocks of tests (roughly equivalent to Pipeline stages) to run together, with a common timeout, and either a "pass" status or an "unstable" status (unstable indicating this block had a non-zero exit status, but that execution of the script should continue). For steps where failure should be deemed critical, the colour code is red instead of yellow, status text says "failed", and there's some extra {{exit 1}}'s thrown in.h2, Groovy script to parse the build log and generate a job status tablePretty much just builds an HTML , pairing "*** start" and "*** end" lines to build the table structure and write the execution time, and adding the most recent test runner output as an at-a-glance summaryh2, Aggregate the data from multiple jobs in a giant table, with a custom pluginthis gives the most dense data view we can manage - 76 steps, 5 architectures, with an at-a-glance look for developers of "did I break tests grouped into X on architecture Y", or "is builder Z misbehaving and in need of attention"I would love to move as much of this crap into a Jenkinsfile as possible. Certainly parts 1 and 2 of the above seem theoretically feasible to me, but there are gaps that means I'd just end up emulating bash _really badly_ in Groovy, rather than taking advantage of Pipeline features (because the Pipeline versions are missing things)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are s
[JIRA] [workflow-plugin] (JENKINS-26522) Annotated block/stage status
Title: Message Title
Jo Shields edited a comment on JENKINS-26522
Re: Annotated block/stage status
Okay, to try & better explain what we're trying to achieve, here's our current implementation, which is split into three parts:h2. Custom logic in the job shell script to annotate resultsroughly speaking, this looks like:{{STEP="System.Security-4.5"}}{{STARTTIME=`date +%s`}}{{echo "*** start: $\{STEP\}"}}{{$ \ {TIMEOUTCMD \ } --signal=ABRT --kill-after=60s 5m make -w -C mcs/class/System.Security run-test TEST_HARNESS_FLAGS=-labels PROFILE=""> \ {STARTTIME \ } | bc)): ${STEP}: \e[42mPassed\e[0m" || echo -e "*** end($(echo $(date +%s) - $ \ {STARTTIME \ } | bc)): ${STEP}: \e[43mUnstable\e[0m"}}This assigns blocks of tests (roughly equivalent to Pipeline stages) to run together, with a common timeout, and either a "pass" status or an "unstable" status (unstable indicating this block had a non-zero exit status, but that execution of the script should continue). For steps where failure should be deemed critical, the colour code is red instead of yellow, status text says "failed", and there's some extra {{exit 1}}'s thrown in.h2, Groovy script to parse the build log and generate a job status tablePretty much just builds an HTML , pairing "*** start" and "*** end" lines to build the table structure and write the execution time, and adding the most recent test runner output as an at-a-glance summaryh2, Aggregate the data from multiple jobs in a giant table, with a custom pluginthis gives the most dense data view we can manage - 76 steps, 5 architectures, with an at-a-glance look for developers of "did I break tests grouped into X on architecture Y", or "is builder Z misbehaving and in need of attention"I would love to move as much of this crap into a Jenkinsfile as possible. Certainly parts 1 and 2 of the above seem theoretically feasible to me, but there are gaps that means I'd just end up emulating bash _really badly_ in Groovy, rather than taking advantage of Pipeline features (because the Pipeline versions are missing things)
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 Issue
[JIRA] [workflow-plugin] (JENKINS-26522) Annotated block/stage status
Title: Message Title
Jo Shields edited a comment on JENKINS-26522
Re: Annotated block/stage status
Okay, to try & better explain what we're trying to achieve, here's our current implementation, which is split into three parts:h2. Custom logic in the job shell script to annotate resultsroughly speaking, this looks like:{{STEP="System.Security-4.5"}}{{STARTTIME=`date +%s`}}{{echo "*** start: $\{STEP\}"}}{{$\{TIMEOUTCMD\} --signal=ABRT --kill-after=60s 5m make -w -C mcs/class/System.Security run-test TEST_HARNESS_FLAGS=-labels PROFILE=""> \ e[42mPassed\e[0m" || echo -e "*** end($(echo $(date +%s) - $\{STARTTIME\} | bc)): ${STEP}: \ \ e[43mUnstable\e[0m"}}This assigns blocks of tests (roughly equivalent to Pipeline stages) to run together, with a common timeout, and either a "pass" status or an "unstable" status (unstable indicating this block had a non-zero exit status, but that execution of the script should continue). For steps where failure should be deemed critical, the colour code is red instead of yellow, status text says "failed", and there's some extra {{exit 1}}'s thrown in.h2, Groovy script to parse the build log and generate a job status tablePretty much just builds an HTML , pairing "*** start" and "*** end" lines to build the table structure and write the execution time, and adding the most recent test runner output as an at-a-glance summaryh2, Aggregate the data from multiple jobs in a giant table, with a custom pluginthis gives the most dense data view we can manage - 76 steps, 5 architectures, with an at-a-glance look for developers of "did I break tests grouped into X on architecture Y", or "is builder Z misbehaving and in need of attention"I would love to move as much of this crap into a Jenkinsfile as possible. Certainly parts 1 and 2 of the above seem theoretically feasible to me, but there are gaps that means I'd just end up emulating bash _really badly_ in Groovy, rather than taking advantage of Pipeline features (because the Pipeline versions are missing things)
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 gro
[JIRA] [workflow-plugin] (JENKINS-26522) Annotated block/stage status
Title: Message Title
Jo Shields edited a comment on JENKINS-26522
Re: Annotated block/stage status
Okay, to try & better explain what we're trying to achieve, here's our current implementation, which is split into three parts:h2. Custom logic in the job shell script to annotate resultsroughly speaking, this looks like:{{STEP="System.Security-4.5" }} {{ STARTTIME=`date +%s` }} {{ echo "*** start: $ \ {STEP \ }" }} {{ ${TIMEOUTCMD} --signal=ABRT --kill-after=60s 5m make -w -C mcs/class/System.Security run-test TEST_HARNESS_FLAGS=-labels PROFILE="" />This assigns blocks of tests (roughly equivalent to Pipeline stages) to run together, with a common timeout, and either a "pass" status or an "unstable" status (unstable indicating this block had a non-zero exit status, but that execution of the script should continue). For steps where failure should be deemed critical, the colour code is red instead of yellow, status text says "failed", and there's some extra {{exit 1}}'s thrown in.h2, Groovy script to parse the build log and generate a job status tablePretty much just builds an HTML , pairing "*** start" and "*** end" lines to build the table structure and write the execution time, and adding the most recent test runner output as an at-a-glance summaryh2, Aggregate the data from multiple jobs in a giant table, with a custom pluginthis gives the most dense data view we can manage - 76 steps, 5 architectures, with an at-a-glance look for developers of "did I break tests grouped into X on architecture Y", or "is builder Z misbehaving and in need of attention"I would love to move as much of this crap into a Jenkinsfile as possible. Certainly parts 1 and 2 of the above seem theoretically feasible to me, but there are gaps that means I'd just end up emulating bash _really badly_ in Groovy, rather than taking advantage of Pipeline features (because the Pipeline versions are missing things)
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.
F
[JIRA] [workflow-plugin] (JENKINS-26522) Annotated block/stage status
Title: Message Title
Jo Shields updated an issue
Jenkins / JENKINS-26522
Annotated block/stage status
Okay, to try & better explain what we're trying to achieve, here's our current implementation, which is split into three parts:
Custom logic in the job shell script to annotate results
roughly speaking, this looks like:
{{STEP="System.Security-4.5" STARTTIME=`date +%s` echo "*** start: $ {STEP}" ${TIMEOUTCMD} --signal=ABRT --kill-after=60s 5m make -w -C mcs/class/System.Security run-test TEST_HARNESS_FLAGS=-labels PROFILE="" && echo -e "*** end($(echo $(date +%s) - ${STARTTIME} | bc)): ${STEP}
: \e[42mPassed\e[0m" || echo -e "*** end($(echo $(date +%s) - $ {STARTTIME}
| bc)): $ {STEP}
: \e[43mUnstable\e[0m"}}
This assigns blocks of tests (roughly equivalent to Pipeline stages) to run together, with a common timeout, and either a "pass" status or an "unstable" status (unstable indicating this block had a non-zero exit status, but that execution of the script should continue). For steps where failure should be deemed critical, the colour code is red instead of yellow, status text says "failed", and there's some extra exit 1's thrown in.
h2, Groovy script to parse the build log and generate a job status table
Pretty much just builds an HTML , pairing "*** start" and "*** end" lines to build the table structure and write the execution time, and adding the most recent test runner output as an at-a-glance summary
h2, Aggregate the data from multiple jobs in a giant table, with a custom plugin
this gives the most dense data view we can manage - 76 steps, 5 architectures, with an at-a-glance look for developers of "did I break tests grouped into X on architecture Y", or "is builder Z misbehaving and in need of attention"
I would love to move as much of this crap into a Jenkinsfile as possible. Certainly parts 1 and 2 of the above seem theoretically feasible to me, but there are gaps that means I'd just end up emulating bash really badly in Groovy, rather than taking advantage of Pipeline features (because the Pipeline versions are missing things)
Change By:
Jo Shields
Attachment:
Screenshot from 2016-04-05 14-30-24.png
Attachment:
[JIRA] [chroot-plugin] (JENKINS-33521) Use textbox for chroot name, and allow environment expansion
Title: Message Title Jo Shields commented on JENKINS-33521 Re: Use textbox for chroot name, and allow environment expansion https://github.com/jenkinsci/chroot-plugin/pull/6 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] [chroot-plugin] (JENKINS-33521) Use textbox for chroot name, and allow environment expansion
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-33521 Use textbox for chroot name, and allow environment expansion Issue Type: Bug Assignee: Unassigned Components: chroot-plugin Created: 14/Mar/16 12:23 PM Priority: Minor Reporter: Jo Shields In order to automate better (and allow matrix jobs), chroots need to be selectable via a parameter (or other environment variable) Add Comment
[JIRA] [chroot-plugin] (JENKINS-33521) Use textbox for chroot name, and allow environment expansion
Title: Message Title Jo Shields updated an issue Jenkins / JENKINS-33521 Use textbox for chroot name, and allow environment expansion Change By: Jo Shields Issue Type: Bug Improvement 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] [chroot-plugin] (JENKINS-33519) Job execution fails if "Clear" enabled & chroot does not exist yet
Title: Message Title Jo Shields commented on JENKINS-33519 Re: Job execution fails if "Clear" enabled & chroot does not exist yet Fixed by https://github.com/jenkinsci/chroot-plugin/pull/5 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] [chroot-plugin] (JENKINS-33519) Job execution fails if "Clear" enabled & chroot does not exist yet
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-33519 Job execution fails if "Clear" enabled & chroot does not exist yet Issue Type: Bug Assignee: Unassigned Components: chroot-plugin Created: 14/Mar/16 11:04 AM Priority: Minor Reporter: Jo Shields If Clear is ticked on a job definition, but the per-job tarball in workspace/tarballname/ hasn't been created yet (e.g. this is the first time a given job has been run on a given node) then the job will fail, with "E: File /jenkinsdir/jobs/jobname/workspace/tarballname/tarballname.tgz does not exist" Add Comment
[JIRA] [parallels-desktop-plugin] (JENKINS-33424) Relies on IP_ADDR value, which is always empty
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-33424 Relies on IP_ADDR value, which is always empty Issue Type: Bug Assignee: Roman Kulikov Components: parallels-desktop-plugin Created: 09/Mar/16 11:33 AM Priority: Minor Reporter: Jo Shields As per https://github.com/Parallels/vagrant-parallels/issues/1#issuecomment-22987003 or http://stackoverflow.com/questions/17896984/how-to-get-the-ip-address-used-by-a-parallels-vm-from-the-host the output from "prlctl" never seems to contain an IP address - but https://github.com/jenkinsci/parallels-desktop-plugin/blob/master/src/main/java/com/parallels/desktopcloud/ParallelsDesktopConnectorSlaveComputer.java#L76-L92 relies on it Perhaps a `prlctl exec` based solution would be more robust? Add Comment
[JIRA] [ec2-plugin] (JENKINS-33350) Does not support Amazon's automatic Windows admin password system
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-33350 Does not support Amazon's automatic Windows admin password system Issue Type: Improvement Assignee: Francis Upton Components: ec2-plugin Created: 07/Mar/16 9:58 AM Environment: Jenkins 1.651 ec2-plugin 1.31 Priority: Minor Reporter: Jo Shields When Amazon spins up a Windows instance, it automatically sets the Administrator password to a per-instance strong password. This password is available to downstream management software like Jenkins, by encrypting that password with the public key of the EC2 user (such that it can be decrypted by the private key). The `ec2-get-password` command in the EC2 CLI does this, as does the Java code here: http://frontier.town/2012/03/java-administrator-password-windows-ec2-instance/ ec2-plugin does not support this mechanism. Instead, the expectation is that you change the Administrator password to a known shared secret in the AMI's userdata, and hardcode that same shared secret in the "Windows Admin Password" field. This password is then identical for all instances of the same AMI, rather than being per-instance. Sending the same password over and over via plain HTTP (the default for this plugin) is questionable security practice.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-30919) Check Docker version
Title: Message Title
Jo Shields edited a comment on JENKINS-30919
Re: Check Docker version
It's an error, not a warning.{ code noformat }Started by user anonymousBuilding in workspace /var/lib/jenkins/jobs/docky/workspaceDocker container e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 started to host the build$ docker exec --tty e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 env[workspace] $ docker exec --tty --user 121: e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 env BUILD_DISPLAY_NAME=#2 BUILD_ID=2 BUILD_NUMBER=2 BUILD_TAG=jenkins-docky-2 BUILD_URL=http://localhost:8080/job/docky/2/ CLASSPATH= EXECUTOR_NUMBER=1 HOME=/root HOSTNAME=e304ee4ac3a5 HUDSON_HOME=/var/lib/jenkins HUDSON_SERVER_COOKIE=a5306de8f7720fc0 HUDSON_URL=http://localhost:8080/ JENKINS_SERVER_COOKIE=a5306de8f7720fc0 JENKINS_URL=http://localhost:8080/ JOB_NAME=docky JOB_URL=http://localhost:8080/job/docky/ NODE_LABELS=master NODE_NAME=master PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin TERM=xterm WORKSPACE=/var/lib/jenkins/jobs/docky/workspace /bin/sh -xe /tmp/hudson1001475129462719389.shflag provided but not defined: --userSee 'docker exec --help'.Build step 'Execute shell' marked build as failureStopping Docker container after build completionFinished: FAILURE{ /code noformat }
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] [docker-custom-build-environment-plugin] (JENKINS-30919) Check Docker version
Title: Message Title
Jo Shields edited a comment on JENKINS-30919
Re: Check Docker version
It's an error, not a warning.{ { code} Started by user anonymousBuilding in workspace /var/lib/jenkins/jobs/docky/workspaceDocker container e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 started to host the build$ docker exec --tty e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 env[workspace] $ docker exec --tty --user 121: e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 env BUILD_DISPLAY_NAME=#2 BUILD_ID=2 BUILD_NUMBER=2 BUILD_TAG=jenkins-docky-2 BUILD_URL=http://localhost:8080/job/docky/2/ CLASSPATH= EXECUTOR_NUMBER=1 HOME=/root HOSTNAME=e304ee4ac3a5 HUDSON_HOME=/var/lib/jenkins HUDSON_SERVER_COOKIE=a5306de8f7720fc0 HUDSON_URL=http://localhost:8080/ JENKINS_SERVER_COOKIE=a5306de8f7720fc0 JENKINS_URL=http://localhost:8080/ JOB_NAME=docky JOB_URL=http://localhost:8080/job/docky/ NODE_LABELS=master NODE_NAME=master PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin TERM=xterm WORKSPACE=/var/lib/jenkins/jobs/docky/workspace /bin/sh -xe /tmp/hudson1001475129462719389.shflag provided but not defined: --userSee 'docker exec --help'.Build step 'Execute shell' marked build as failureStopping Docker container after build completionFinished: FAILURE {/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] [docker-custom-build-environment-plugin] (JENKINS-30919) Check Docker version
Title: Message Title
Jo Shields commented on JENKINS-30919
Re: Check Docker version
It's an error, not a warning.
{{Started by user anonymous Building in workspace /var/lib/jenkins/jobs/docky/workspace Docker container e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 started to host the build $ docker exec --tty e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 env [workspace] $ docker exec --tty --user 121: e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 env BUILD_DISPLAY_NAME=#2 BUILD_ID=2 BUILD_NUMBER=2 BUILD_TAG=jenkins-docky-2 BUILD_URL=http://localhost:8080/job/docky/2/ CLASSPATH= EXECUTOR_NUMBER=1 HOME=/root HOSTNAME=e304ee4ac3a5 HUDSON_HOME=/var/lib/jenkins HUDSON_SERVER_COOKIE=a5306de8f7720fc0 HUDSON_URL=http://localhost:8080/ JENKINS_SERVER_COOKIE=a5306de8f7720fc0 JENKINS_URL=http://localhost:8080/ JOB_NAME=docky JOB_URL=http://localhost:8080/job/docky/ NODE_LABELS=master NODE_NAME=master PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin TERM=xterm WORKSPACE=/var/lib/jenkins/jobs/docky/workspace /bin/sh -xe /tmp/hudson1001475129462719389.sh flag provided but not defined: --user See 'docker exec --help'. Build step 'Execute shell' marked build as failure Stopping Docker container after build completion Finished: 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] [global-post-script-plugin] (JENKINS-31907) Does not expose GIT_ variables
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-31907 Does not expose GIT_ variables Issue Type: Bug Assignee: Hao CHEN Components: global-post-script-plugin Created: 04/Dec/15 4:43 PM Priority: Minor Reporter: Jo Shields SVN_REVISION and SVN_URL are all well and good, but it's 2015 and access to GIT_ equivalents would be nice. [ERROR] Failed to execute: downstream_job_trigger.groovy, No such property: $GIT_URL for class: Script1 Add Comment
[JIRA] [core] (JENKINS-31663) Cannot load job summary page for job with huge history
Title: Message Title Jo Shields commented on JENKINS-31663 Re: Cannot load job summary page for job with huge history Definitely a regression, is super fast when downgraded to LTS 1.625.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-31663) Cannot load job summary page for job with huge history
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-31663 Cannot load job summary page for job with huge history Issue Type: Bug Assignee: Unassigned Components: core Created: 19/Nov/15 7:12 PM Environment: jenkins 1.638 on Ubuntu 14.04 Priority: Minor Reporter: Jo Shields We have a job with 141935 builds (at time of writing). Clicking the latest succeeded or failed builds from the main view works fine, and is fast. The "previous build" links are fast too. But I can't load the job summary page (i.e. $JENKINS_URL/job/jobname), or manage it, or anything on a per-job rather than per-build basis. Anecdotally, the problem seems to have started since we upgraded to 1.638 (for the security vulnerability) from 1.632
[JIRA] [s3-plugin] (JENKINS-29582) S3 artifact download fails due to null selector
Title: Message Title Jo Shields commented on JENKINS-29582 Re: S3 artifact download fails due to null selector It's fixed in https://github.com/jenkinsci/s3-plugin/pull/63 FWIW. 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] [workflow-plugin] (JENKINS-26523) Allow yellow "unstable" state from a step
Title: Message Title Jo Shields commented on JENKINS-26523 Re: Allow yellow "unstable" state from a step "A per-FlowNode status would only be useful if you wished to have a number of different stages that could individually be marked as unstable or even failing without preventing subsequent stages from running and being displayed as stable, and if the console log were inadequate to note this (even with specialized markup such as colors)." I wish to have a number of different stages that could individually be marked as unstable or even failing without preventing subsequent stages from running and being displayed as stable, and if the console log is inadequate to note this (even with specialized markup such as colors). 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] [workflow-plugin] (JENKINS-26523) Allow yellow "unstable" state from a step
Title: Message Title Jo Shields edited a comment on JENKINS-26523 Re: Allow yellow "unstable" state from a step bq. "A per-FlowNode status would only be useful if you wished to have a number of different stages that could individually be marked as unstable or even failing without preventing subsequent stages from running and being displayed as stable, and if the console log were inadequate to note this (even with specialized markup such as colors)."I wish to have a number of different stages that could individually be marked as unstable or even failing without preventing subsequent stages from running and being displayed as stable, and if the console log is inadequate to note this (even with specialized markup such as colors). 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-30694) Support for GitHub Build Trigger in Workflow jobs
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-30694 Support for GitHub Build Trigger in Workflow jobs Issue Type: Bug Assignee: Kanstantsin Shautsou Components: github-plugin Created: 29/Sep/15 11:54 AM Priority: Minor Reporter: Jo Shields The "Build when a change is pushed to GitHub" build trigger is not available in Workflow jobs, but would be very useful if possible. Add Comment This message was sent by Atlassian JIRA (v6
[JIRA] [build-alias-setter-plugin] (JENKINS-30426) Allow overwrite of aliases
Title: Message Title Jo Shields commented on JENKINS-30426 Re: Allow overwrite of aliases https://github.com/jenkinsci/build-alias-setter-plugin/pull/1 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-alias-setter-plugin] (JENKINS-30426) Allow overwrite of aliases
Title: Message Title Jo Shields commented on JENKINS-30426 Re: Allow overwrite of aliases Some investigation: It does allow "overwriting" of aliases. The problem is in PermalinkStorage.java, where the stored aliases returned by getPermalinks() are not in any coherent order (ie they should be ordered by buildNumber but they aren't) 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-alias-setter-plugin] (JENKINS-30426) Allow overwrite of aliases
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-30426 Allow overwrite of aliases Issue Type: Bug Assignee: Oliver Gondža Components: build-alias-setter-plugin Created: 12/Sep/15 10:56 AM Priority: Minor Reporter: Jo Shields We have an artifact which changes ABI occasionally, and want a dependable URL which links to the most recent build of that artifact. The plan was to use the build alias setter plugin, such that https://my.jenkins/job/myjob/ABI-137/s3/download/library-137-latest.tar.gz would always point to the most recent build of that ABI. However, despite the claims in the logs: 12:30:06 BuildAliasSetter: setting build aliases [ABI-137] the URL still points to the first, not most recent, build with that alias. Add Comment
[JIRA] [s3-plugin] (JENKINS-29582) S3 artifact download fails due to null selector
Title: Message Title Jo Shields commented on JENKINS-29582 Re: S3 artifact download fails due to null selector Okay, https://github.com/directhex/s3-plugin/commit/11b22c150957cf6f4ff435b1461f6c80d1b2237d seems to cover all bases for me. 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] [s3-plugin] (JENKINS-29582) S3 artifact download fails due to null selector
Title: Message Title Jo Shields updated an issue Jenkins / JENKINS-29582 S3 artifact download fails due to null selector Change By: Jo Shields Summary: S3 artifact download fails if "delete workspace" enabled due to null selector 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] [s3-plugin] (JENKINS-29582) S3 artifact download fails if "delete workspace" enabled
Title: Message Title Jo Shields commented on JENKINS-29582 Re: S3 artifact download fails if "delete workspace" enabled In copyartifact, there's a fallback when Selector is null: https://github.com/jenkinsci/copyartifact-plugin/blob/master/src/main/java/hudson/plugins/copyartifact/CopyArtifact.java#L120-L122 There's no fallback in s3. The previous comment relates to it, in that Selector is not selectable currently (because the jelly files point to non-existent code in copyartifact, Jenkins simply skips the entire tag) 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] [s3-plugin] (JENKINS-29582) S3 artifact download fails if "delete workspace" enabled
Title: Message Title Jo Shields commented on JENKINS-29582 Re: S3 artifact download fails if "delete workspace" enabled I strongly suspect this is related: https://issues.jenkins-ci.org/browse/JENKINS-28094 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] [s3-plugin] (JENKINS-29582) S3 artifact download fails if "delete workspace" enabled
Title: Message Title Jo Shields commented on JENKINS-29582 Re: S3 artifact download fails if "delete workspace" enabled Yeah, seems I was wrong about the cause - it started at the same time as I installed the WS cleanup plugin in my debug environment, but hasn't gone away now I've uninstalled it. I don't know what's causing selector to be null. 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] [s3-plugin] (JENKINS-29582) S3 artifact download fails if "delete workspace" enabled
Title: Message Title Jo Shields commented on JENKINS-29582 Re: S3 artifact download fails if "delete workspace" enabled Sigh, not complete. But along those lines, anyway. Will keep poking. 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] [s3-plugin] (JENKINS-29582) S3 artifact download fails if "delete workspace" enabled
Title: Message Title Jo Shields commented on JENKINS-29582 Re: S3 artifact download fails if "delete workspace" enabled https://github.com/directhex/s3-plugin/commit/279bb125996a676cd7724178a28835590fd8a8f9 seems to work (thieved from copyartifact-plugin) 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] [s3-plugin] (JENKINS-29582) S3 artifact download fails if "delete workspace" enabled
Title: Message Title Jo Shields commented on JENKINS-29582 Re: S3 artifact download fails if "delete workspace" enabled Okay, this is super weird. The S3CopyArtifact @DataBoundConstructor is getting fed null as its BuildSelector parameter, but only when the workspace is deleted pre-build. And I don't know why. So the NPE comes from selector.getBuild() being called when selector is null. 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] [s3-plugin] (JENKINS-29582) S3 artifact download fails if "delete workspace" enabled
Title: Message Title
Jo Shields updated an issue
Jenkins / JENKINS-29582
S3 artifact download fails if "delete workspace" enabled
Change By:
Jo Shields
{ { noformat} Started by user anonymousBuilding in workspace /home/directhex/Projects/s3-plugin/work/workspace/downloader-testDeleting project workspace... doneERROR: Build step failed with exceptionjava.lang.NullPointerException at hudson.plugins.s3.S3CopyArtifact.perform(S3CopyArtifact.java:169) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381)Build step 'S3 Copy Artifact' marked build as failureFinished: FAILURE {noformat } }
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] [s3-plugin] (JENKINS-29582) S3 artifact download fails if "delete workspace" enabled
Title: Message Title
Jo Shields updated an issue
Jenkins / JENKINS-29582
S3 artifact download fails if "delete workspace" enabled
Change By:
Jo Shields
{{ Started by user anonymousBuilding in workspace /home/directhex/Projects/s3-plugin/work/workspace/downloader-testDeleting project workspace... doneERROR: Build step failed with exceptionjava.lang.NullPointerException at hudson.plugins.s3.S3CopyArtifact.perform(S3CopyArtifact.java:169) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381)Build step 'S3 Copy Artifact' marked build as failureFinished: 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] [s3-plugin] (JENKINS-29582) S3 artifact download fails if "delete workspace" enabled
Title: Message Title
Jo Shields created an issue
Jenkins / JENKINS-29582
S3 artifact download fails if "delete workspace" enabled
Issue Type:
Bug
Assignee:
Michael Watt
Components:
s3-plugin, ws-cleanup-plugin
Created:
23/Jul/15 7:20 AM
Priority:
Minor
Reporter:
Jo Shields
{{Started by user anonymous Building in workspace /home/directhex/Projects/s3-plugin/work/workspace/downloader-test
Deleting project workspace... done
ERROR: Build step failed with exception java.lang.NullPointerException at hudson.plugins.s3.S3CopyArtifact.perform(S3CopyArtifact.java:169) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381) Build step 'S3 Copy Artifact' marked build as failure Finished: FAILURE}}
[JIRA] [s3-plugin] (JENKINS-29532) Does not export via JSON API
Title: Message Title Jo Shields commented on JENKINS-29532 Re: Does not export via JSON API Initial implementation: https://github.com/directhex/s3-plugin/commit/cc4fba5b2031389c3b88a5eeb245bcf0eb03169f Current issues: It attaches inside actions[] rather than at the same depth (which is wrong) - there is an empty artifacts[] too for non-s3 artifacts. Maybe this should export a specific s3artifacts key? Would welcome ideas. 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] [s3-plugin] (JENKINS-29533) Does not implement checkRoles(RoleChecker checker) from remoting-2.47
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-29533 Does not implement checkRoles(RoleChecker checker) from remoting-2.47 Issue Type: Bug Assignee: Michael Watt Components: s3-plugin Created: 21/Jul/15 12:06 PM Priority: Minor Reporter: Jo Shields The current S3 plugin cannot compile against the current remoting plugin, due to API changes from https://github.com/jenkinsci/remoting/commit/944fb8a801f8d39efbbe21b46401859a7f2d76c3 Add Comment
[JIRA] [s3-plugin] (JENKINS-29532) Does not export via JSON API
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-29532 Does not export via JSON API Issue Type: Bug Assignee: Michael Watt Components: s3-plugin Created: 21/Jul/15 12:03 PM Priority: Minor Reporter: Jo Shields Users can get information on all build artifacts for non-S3 artifacts, via JENKINSURL/job/JOBNAME/api/json?depth=2 With S3 artifacts, the relevant JSON is empty: "artifacts" : [ ], And there's no JSON entry with information on where the S3 artifacts can be found. Add Comment
[JIRA] [copyartifact-plugin] (JENKINS-29528) ABI break in copyartifact-1.34
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-29528 ABI break in copyartifact-1.34 Issue Type: Bug Assignee: Michael Watt Components: copyartifact-plugin, s3-plugin Created: 21/Jul/15 9:19 AM Priority: Minor Reporter: Jo Shields Copyartifact 1.34 includes this commit: https://github.com/jenkinsci/copyartifact-plugin/commit/f5647fcb445c83b1cfc80d83801be41e774e3770 s3-plugin consumes this symbol, in current git master: https://github.com/jenkinsci/s3-plugin/blob/master/src/main/java/hudson/plugins/s3/S3CopyArtifact.java#L176 Add Comment
[JIRA] [jobconfighistory-plugin] (JENKINS-28966) "Oops" error in Jelly tag viewing job history
Title: Message Title
Jo Shields created an issue
Jenkins / JENKINS-28966
"Oops" error in Jelly tag viewing job history
Issue Type:
Bug
Assignee:
Mirko Friedenhagen
Components:
jobconfighistory-plugin
Created:
18/Jun/15 1:28 PM
Environment:
Jenkins 1.617, JRE 7u79-2.5.5-0ubuntu0.14.04.2
Priority:
Major
Reporter:
Jo Shields
I'm fine viewing global config stuff, but in my test job changes, I get the following exception when clicking a given job's "Job Config History" link:
{{javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.617.jar!/lib/layout/main-panel.jelly:36:21: hudson/maven/MavenModule at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.
[JIRA] [elastic-axis-plugin] (JENKINS-27420) Allow for "any node matching label", not just "all nodes matching label"
Title: Message Title Jo Shields commented on JENKINS-27420 Re: Allow for "any node matching label", not just "all nodes matching label" https://github.com/jenkinsci/elastic-axis-plugin/pull/4 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] [elastic-axis-plugin] (JENKINS-28694) "node label" tooltip fails to parse comma-separated list
Title: Message Title Jo Shields commented on JENKINS-28694 Re: "node label" tooltip fails to parse comma-separated list https://github.com/jenkinsci/elastic-axis-plugin/pull/3 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] [elastic-axis-plugin] (JENKINS-28694) "node label" tooltip fails to parse comma-separated list
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-28694 "node label" tooltip fails to parse comma-separated list Issue Type: Bug Assignee: Unassigned Components: elastic-axis-plugin Created: 02/Jun/15 2:42 PM Priority: Minor Reporter: Jo Shields The help for the "node label" field states as its example: "label_1,label_2" This example will cause the following tooltip: "There’s no slave/cloud that matches this assignment. Did you mean ‘label_1’ instead of ‘label_1,label_2’?" I believe this is caused by a bug on https://github.com/jenkinsci/elastic-axis-plugin/blob/master/src/main/java/org/jenkinsci/plugins/elasticaxisplugin/ElasticAxis.java#L104 - the form validation is tokenized on " " not "," Add Comment
[JIRA] [core] (JENKINS-21099) Don't give useless build time estimates by considering failed builds' durations
Jo Shields commented on JENKINS-21099 Don't give useless build time estimates by considering failed builds' durations Using failed builds is meaningless. I don't create jobs designed to fail, I create jobs designed to succeed. Failures are always outliers, by definition, even if the last six builds have been failures. It is entirely useless to me and my users to be given a 20 minute estimate on a 2-hour 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] [subversion-plugin] (JENKINS-673) SCM "catch up" feature
Jo Shields commented on JENKINS-673 SCM "catch up" feature I've made some progress. I now have a local fork of the Git Plugin with a "Wrench" BuildChooser - it returns an array of intermediate jobs up the chain when queried (DefaultBuildChooser blindly returns a 1-element array containing HEAD). There's code to handle candidate commit arrays, but the code is really stupid, and that's where I'm currently stuck - it (racily, so sometimes it messes up) builds HEAD and HEAD~1, but nothing earlier regardless of how many earlier commits there are. This is at https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L927-936 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] [build-name-setter-plugin] (JENKINS-27542) Pass parent job name to triggered jobs
Jo Shields created JENKINS-27542 Pass parent job name to triggered jobs Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: build-name-setter-plugin Created: 23/Mar/15 12:07 PM Description: I have a job monitoring a git repository, which triggers jobs which are not looking at git. I currently rename builds on the git job to the abbreviated sha1. I would like to rename the child jobs too. I can't use a parameter file or environment variable, as the file i have created with the hash in it doesn't exist until after the copy artefact plugin has operated, during the build steps - which is too late. There should be a simple PARENT_JOB_NAME variable I can use. Project: Jenkins Priority: Minor Reporter: Jo Shields 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-plugin] (JENKINS-27460) Single-commit changelog mode
Jo Shields created JENKINS-27460 Single-commit changelog mode Issue Type: New Feature Assignee: Nicolas De Loof Components: git-plugin Created: 17/Mar/15 12:18 PM Description: When viewing a build, the Git plugin creates a changelog to display under the "changes" heading, roughly comprising a numeric list of git commit messages between the last repo pull and the current pull. It is possible to override this with the "Calculate changelog against a specific branch" additional behaviour. However, this is too complex for the scenario I need (I've got a per-commit builder, which splits commits which were bundled together by polling/github pushes into individual commitids) - I just want this to show the single commit log message for the current commit. Project: Jenkins Priority: Minor Reporter: Jo Shields 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] [elastic-axis-plugin] (JENKINS-27420) Allow for "any node matching label", not just "all nodes matching label"
Jo Shields created JENKINS-27420 Allow for "any node matching label", not just "all nodes matching label" Issue Type: New Feature Assignee: Unassigned Components: elastic-axis-plugin Created: 13/Mar/15 3:28 PM Description: I have an elastic axis "label", with node label "debian-ppc64el,centos-s390x" What I want is for any 1 node matching debian-ppc64el, AND any 1 node matching centos-s390x, to be used for the build, such that the output is available at the URL http://...blabla/label=centos-s390x/ and http://...blabla/label=debian-ppc64el/ Instead, Elastic Axis has expanded my labels, created http://...blabla/label=s390xbuilder-1-hostname/ and http://...blabla/label=s390xbuilder-2-hostname/ entries, and tries to build on both machines (a waste of time/resources) Project: Jenkins Priority: Minor Reporter: Jo Shields 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] [subversion-plugin] (JENKINS-673) SCM "catch up" feature
Jo Shields commented on JENKINS-673 SCM "catch up" feature 7 years, and no activity beyond half-baked workarounds. So. From where I'm sat, there are two issues to resolve: A way to inject builds with given revisions, without requiring a parameterized build, OR making parameters optional so if Jenkins detects "I am missing these intermediate commits, I will add jobs to build them" it can do so without breaking workflow for non-parameterised default behaviour Maintain some knowledge of "the last master I know about". If Jenkins knows it built revision r1, then polls to discover revision r10, it needs to be able to inject builds for r2..r10 without being confused if r12 appears in the next round of polling (i.e. the record needs to be 'newest commit I know about', not 'last commit I acted upon'). This value should be user-visible in the project settings, so newly created projects don't try to catch up on 10 years of commits. Importantly, building commits in precise order is irrelevant - you care whether given commits have been tested, not when they were tested. The order becomes especially irrelevant if you use the build name plugin to use commitid for build revision names, not an incrementing numeric value as is the default. A bunch of this plumbing is already done - we can poll the SCM. Some SCM plugins clearly have knowledge of whether revisions have already been done or not (e.g. hudson/plugins/git/util/DefaultBuildChooser.java#L134). The less-implemented part is the first one - injecting the intermediate jobs into the build queue, not just the latest 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] [xvfb-plugin] (JENKINS-26848) Does not actually randomize DISPLAY
Jo Shields commented on JENKINS-26848 Does not actually randomize DISPLAY Never mind, I'm a big boy and I can build from a git tag. Seems to work - https://jenkins.mono-project.com/job/test-mono-mainline/993/label=debian-armhf/console and https://jenkins.mono-project.com/job/test-mono-mainline/993/label=debian-armel/console you can see one build using :1401 and one using :1501. Yay! 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] [xvfb-plugin] (JENKINS-26848) Does not actually randomize DISPLAY
Jo Shields commented on JENKINS-26848 Does not actually randomize DISPLAY Doesn't seem to be in http://ftp-chi.osuosl.org/pub/jenkins/updates/experimental/update-center.json or http://updates.jenkins-ci.org/download/plugins/xvfb/ - do you have a direct link to the .hpi I can use? 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] [xvfb-plugin] (JENKINS-26848) Does not actually randomize DISPLAY
Jo Shields commented on JENKINS-26848 Does not actually randomize DISPLAY Amazing. I'll try that next time I'm near a computer - I'd rather not break a production system from a smartphone 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] [xvfb-plugin] (JENKINS-26848) Does not actually randomize DISPLAY
Jo Shields commented on JENKINS-26848 Does not actually randomize DISPLAY Same jobs on both 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] [xvfb-plugin] (JENKINS-26848) Does not actually randomize DISPLAY
Jo Shields commented on JENKINS-26848 Does not actually randomize DISPLAY I have a uniquely awkward set of conditions. I have boards with 2 ssh daemons, on different ports, connected as single-executor nodes in Jenkins. It's done this way because the second instance is a slightly different CPU architecture/ABI, and I can't have that distinction in Jenkins between executors on the same node. The two environments are totally separate... Except for sharing port space, so if the bare system uses Xvfb on port 6001, running Xvfb on 6001 in the chroot will fail (and fail the 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] [xvfb-plugin] (JENKINS-26848) Does not actually randomize DISPLAY
Jo Shields created JENKINS-26848 Does not actually randomize DISPLAY Issue Type: Bug Assignee: zregvart Components: xvfb-plugin Created: 08/Feb/15 12:07 AM Description: The docs say displayName is "(default) choosen by random" The code comments on the variable say "DISPLAY name, if NULL chosen by random." The actual contents of src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java L470 say that it will always use executor.getNumber() + displayNameOffset - which always returns displayNameOffset (default 1). As a result, DISPLAY is always 1. Using autoDisplayName is not an option, because it requires a version of Xvfb far too new for our builders (1.14 I think?) Project: Jenkins Priority: Minor Reporter: Jo Shields 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] [build-name-setter-plugin] (JENKINS-26811) Pull Request Builder integration
Jo Shields created JENKINS-26811 Pull Request Builder integration Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: build-name-setter-plugin Created: 05/Feb/15 5:07 PM Description: It would be amaaazing if this plugin could retrieve the pull request number stored in the GitHub Pull Request Builder plugin, if available. Project: Jenkins Priority: Minor Reporter: Jo Shields 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] [matrix-project-plugin] (JENKINS-26631) Pointless duplicate checkouts, causing problems on space-constrained builders
Jo Shields created JENKINS-26631 Pointless duplicate checkouts, causing problems on space-constrained builders Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 27/Jan/15 12:48 PM Description: Whenever you run a matrix job, regardless of how many buildbots will actually get picked by label/node, when executing there is a "parent" job and one or more "child" jobs. So if I have a matrix project called "test", with labels "amd64" and "i386" selected, I will end up with three executing jobs - "test", "test > i386" and "test > amd64". Sometimes, the "parent" job and one of the "child" jobs are on the same host. This is fine. However, often, they are on different hosts. When this happens, a full SCM checkout happens on both the child host and the parent host. Even if the matrix labels mean the parent can never run the job it is parent to by itself, it will have a full source checkout - potentially several gigabytes - used uselessly. For example, "ppc64el-specific-test" might be parented on an amd64 host, meaning a full SCM checkout on that amd64 host which is never needed and never used and never cleaned. I'm running some very space-constrained builders, and this behaviour is killing me. I don't need more than half the space in my /var/lib/jenkins/workspace on my ppc64el host to contain jobs that will never be built on that host, and I can't imagine who would. Project: Jenkins Priority: Minor Reporter: Jo Shields 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] [xvfb-plugin] (JENKINS-26555) Workflow plugin support
Jo Shields created JENKINS-26555 Workflow plugin support Issue Type: Bug Assignee: zregvart Components: xvfb-plugin Created: 22/Jan/15 4:50 PM Description: It would be nice to have this integrated nicely into Workflow - we need Xvfb for our test suite to run. Project: Jenkins Priority: Minor Reporter: Jo Shields 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] [workflow-plugin] (JENKINS-26523) Allow yellow "unstable" state from a step
Jo Shields created JENKINS-26523 Allow yellow "unstable" state from a step Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 21/Jan/15 9:48 AM Description: The xUnit plugin allows for a yellow "unstable" state, between red "FAIL" and blue "OK". This is useful for test-suite steps, to help developers immediately distinguish between "I broke one of 40,000 unit tests" and "I caused compilation to fail entirely". It would help if there were an easy way to assign an unstable state as the result of a step, especially a shell step (e.g. if we could check for a magic exit code to mark a step as unstable rather than failed) Project: Jenkins Priority: Minor Reporter: Jo Shields 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] [workflow-plugin] (JENKINS-26522) Annotated block results
Jo Shields created JENKINS-26522 Annotated block results Issue Type: Bug Assignee: Jesse Glick Attachments: wrench.png Components: workflow-plugin Created: 21/Jan/15 9:42 AM Description: It is often useful to provide more information up-front than a simple red or green "this step passed" or "this step failed". Our current in-house CI software has a "summary" field in its "Running Steps" equivalent, which can be filled with other info when a step finishes. For example, we have a step "upload-to-storage" which can optionally replace a "/latest/" symlink to the output it just uploaded. Either replacing or not replacing the symlink is correct, so we populate our "summary" field with the decision taken. I've attached an example from our current CI system - note that by allowing a step to populate its own summary, it means all pertinent information is available immediately to developers, on one page, rather than needing to always click through to log output for high-level information. Project: Jenkins Priority: Minor Reporter: Jo Shields 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] [workflow-plugin] (JENKINS-26521) timeout step should support breaking on inactivity, not just a fixed duration
Jo Shields created JENKINS-26521 timeout step should support breaking on inactivity, not just a fixed duration Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 21/Jan/15 9:23 AM Description: Some of our test-suite items can occasionally deadlock, causing a build to never finish. The Build Timeout Plugin (http://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin) supports failing a job when nothing happens (i.e. no log output) for a sufficient length of time. It would be good to get this behaviour in Workflow. Project: Jenkins Priority: Minor Reporter: Jo Shields 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.
