[JIRA] (JENKINS-40072) Multibranch creates multiple new directories
Title: Message Title Matthew DeTullio resolved as Duplicate Jenkins / JENKINS-40072 Multibranch creates multiple new directories Change By: Matthew DeTullio Status: Open Resolved Resolution: Duplicate 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-41360) Steps need to be whitelisted and/or grouped
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41360 Steps need to be whitelisted and/or grouped Issue Type: Improvement Assignee: Keith Zantow Components: blueocean-pipeline-editor-plugin, blueocean-plugin Created: 2017/Jan/24 7:58 AM Priority: Major Reporter: Michael Neale Currently the way steps are displayed is inviting users to do probably not what they want to do. There should be a few curated set of steps highlighted at the top (eg shell). Some steps may have to be hidden (eg the 'waitUntil' I don't think can ever actualy work with declarative - still looking into that). There are likely others that are irrelevant to declarative that should ideally not be shown. At the very least sorting them in some curated way would be ideal. Add Comment
[JIRA] (JENKINS-41359) Global methods in pipeline shared-library fails when invoked
Title: Message Title
Tor Christian Solevågseide created an issue
Jenkins / JENKINS-41359
Global methods in pipeline shared-library fails when invoked
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2017/Jan/24 7:51 AM
Environment:
Jenkins version 2.41 Pipeline plugin 2.4
Priority:
Minor
Reporter:
Tor Christian Solevågseide
As documented in https://jenkins.io/doc/book/pipeline/shared-libraries/, I've created the file vars/acme.groovy in a library project checked into our SVN.
def setName(value) {
this.name = value;
}
def getName() {
return this.name;
}
def caution(message) {
echo "Hello, ${this.name}! CAUTION: ${message}"
}
My pipeline script in a Jenkins2 pipeline project:
acme.name = 'Alice'
echo acme.name
acme.caution 'The queen is angry!'
The two first lines, setting and getting the name works fine. But when I include the last line, calling the "caution" function, the script fails with
hudson.remoting.ProxyException:
[JIRA] (JENKINS-41358) Round tripping missing data
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41358 Round tripping missing data Issue Type: Bug Assignee: Keith Zantow Components: blueocean-pipeline-editor-plugin, blueocean-plugin Created: 2017/Jan/24 7:50 AM Priority: Major Reporter: Michael Neale On a first look, encountered a few potential round trip problems: If you set the agent at the stage level and 'load' it, when you round trip it is stripped if you use something like 'sh "hey"' it converts the double quotes to single quotes (aside - how will we set the literal or not state of a value?) Add Comment
[JIRA] (JENKINS-41357) Testresults displayed wrong on parallel branches
Title: Message Title Dennis Truemper created an issue Jenkins / JENKINS-41357 Testresults displayed wrong on parallel branches Issue Type: Bug Assignee: Unassigned Attachments: TestOutput.rar, VisualInformation.jpg Components: junit-plugin Created: 2017/Jan/24 7:45 AM Environment: OS: Windows Server 2012 64bit Java: Oracle Java 8 Update 111 (64bit) JUnit Plugin: 1.19 Jenkins 2.19.4 Installed with Windows installer, no proxy, no container (except there is one installed by default) Tested with current Chrome, Firefox and Edge Priority: Minor Reporter: Dennis Truemper I have a pipelinejob with multiple branches. Each branch produces an report.xml file. All the results get published, but the overview shows no failed tests, even if there are some in branches. The first branch has no errors. I add Data from a sample case where branch 0 to 4 have 0 errors and branch 5 has 1 error. I changed the test data to keep it simple, but the structure is untouched. This is in TestOutput.rar. The picture VisualInformation shows the overall Result from the jobPage in the upper part. In the lower part you can see the actual test result, which shows the error wich was missing.
[JIRA] (JENKINS-41317) Crash when opening branches page of Bitbucket branch source
Title: Message Title Emil Styrke commented on JENKINS-41317 Re: Crash when opening branches page of Bitbucket branch source Excellent! 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-40607) Fix Findbugs errors
Title: Message Title Evaristo Gutierrez updated JENKINS-40607 Jenkins / JENKINS-40607 Fix Findbugs errors Change By: Evaristo Gutierrez Status: In Review 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] (JENKINS-41356) Need to be able to delete a whole stage
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41356 Need to be able to delete a whole stage Issue Type: Bug Assignee: Keith Zantow Components: blueocean-pipeline-editor-plugin, blueocean-plugin Created: 2017/Jan/24 7:24 AM Priority: Minor Reporter: Michael Neale I named my stage something horrible and unforgivable, yet I am unable to delete it (stack trace results). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41355) Default agent to 'any'
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41355 Default agent to 'any' Change By: Michael Neale Component/s: blueocean-pipeline-editor-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41355) Default agent to 'any'
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41355 Default agent to 'any' Issue Type: Task Assignee: Keith Zantow Components: blueocean-plugin Created: 2017/Jan/24 7:22 AM Priority: Minor Reporter: Michael Neale In the interest of "just working", the agent setting should default to "any", vs an invalid empty non assigned state as it is now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40721) Wrappers provided by plugins not working correctly
Title: Message Title Liam Newman commented on JENKINS-40721 Re: Wrappers provided by plugins not working correctly Copying in my comment on the PR: Unless you plan to make this change work everywhere in Declarative, do not do it now. It is another special case for documentation and a support. I understand this was confusing for the reporter, but just as many people will find it confusing the other way. The last thing we need is more special cases: you don't need empty parens here, but you do need them there, oh, but not that other place. Groovy overall makes parens optional but not for methods with no parameters. I see zero benefit to innovating away from that. Let's try to stick with either "It works just like it does in plain old Groovy or it is not allowed". This is something that should at best be post-1.0 - it is a non-breaking change to make the empty parens optional later. On the other hand, if you make them optional now, it is a breaking change if you find some reason why they are needed later. This feature is already coming in hot enough. 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-40897) WARNINGs are filling the log
Title: Message Title Christopher Williams edited a comment on JENKINS-40897 Re: WARNINGs are filling the log I have a similar issue but even worse. Delivery pipeline plugin version: 0.10.2 Where LOG.log(Level.WARNING, "Failed to evaluate token using token-macro plugin", e) in src/main/java/se/diabol/jenkins/pipeline/token/TokenUtils.java flooded (JENKINS-40763) our stdout with stack-traces in our docker container that runs a Jenkins master. This brought it down because all stdout in a docker container is stored to disk and caused us to run out of disk (450GB). Thank goodness for Logrotate ;-)HälsarChris 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-41354) Git environment variables are not accessible
Title: Message Title Deekshith Kumar created an issue Jenkins / JENKINS-41354 Git environment variables are not accessible Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2017/Jan/24 6:22 AM Environment: Jenkins ver. 1.639 git plugin 3.0.1 Priority: Blocker Reporter: Deekshith Kumar Below echo command is printing empty echo "GIT_PREVIOUS_COMMIT:" $GIT_PREVIOUS_COMMIT echo "GIT_COMMIT:" $GIT_COMMIT output: GIT_PREVIOUS_COMMIT: GIT_COMMIT: Add Comment
[JIRA] (JENKINS-41353) Unable to run ECS Slave for jenkins job
Title: Message Title
rajasekaran radhakrishnan commented on JENKINS-41353
Re: Unable to run ECS Slave for jenkins job
Hi Team, My task is started now but immediately that task will be stopped. I dont know the reason can you just give some suggestion to fix this issue. Jenkins Logs: Jan 24, 2017 6:12:22 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResources INFO: Resources found in instance arn:aws:ecs:us-east-1:274091617646:container-instance/096140a7-b534-446b-a2a3-85e196cf697c: [ {Name: CPU,Type: INTEGER,DoubleValue: 0.0,LongValue: 0,IntegerValue: 1024,StringSetValue: []} , {Name: MEMORY,Type: INTEGER,DoubleValue: 0.0,LongValue: 0,IntegerValue: 995,StringSetValue: []} , {Name: PORTS,Type: STRINGSET,DoubleValue: 0.0,LongValue: 0,IntegerValue: 0,StringSetValue: [22, 2376, 2375, 51678, 51679]} , {Name: PORTS_UDP,Type: STRINGSET,DoubleValue: 0.0,LongValue: 0,IntegerValue: 0,StringSetValue: []} ] Jan 24, 2017 6:12:22 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResources INFO: Instance arn:aws:ecs:us-east-1:274091617646:container-instance/096140a7-b534-446b-a2a3-85e196cf697c has 995mb of free memory. 512mb are required Jan 24, 2017 6:12:22 AM com.cloudbees.jenkins.plugins.amazonecs.ECSService waitForSufficientClusterResources INFO: Instance arn:aws:ecs:us-east-1:274091617646:container-instance/096140a7-b534-446b-a2a3-85e196cf697c has 1,024 units of free cpu. 20 units are required Jan 24, 2017 6:12:22 AM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback call INFO: Created Slave: ecs-cloud-2b525d006ba Jan 24, 2017 6:12:22 AM com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback call INFO: Slave ecs-cloud-2b525d006ba - Slave Task Started : arn:aws:ecs:us-east-1:274091617646:task/dd540fc4-8fa8-4261-8e02-4df1f620ab10 ECS-Logs: aws.com 2017-01-24T05:28:04Z [INFO] Creating poll dialer, host: ecs-t-3.us-east-1.amazon aws.com 2017-01-24T05:28:14Z [INFO] Saving state! module="statemanager" 2017-01-24T05:39:04Z [INFO] Creating poll dialer, host: ecs-t-3.us-east-1.amazonaws.com 2017-01-24T05:43:28Z [INFO] Creating poll dialer, host: ecs-a-3.us-east-1.amazonaws.com 2017-01-24T05:50:04Z [INFO] Creating poll dialer, host: ecs-t-3.us-east-1.amazonaws.com 2017-01-24T05:58:04Z [INFO] No eligible images for deletion for this cleanup cycle 2017-01-24T05:58:04Z [INFO] End of eligible images for deletion Slave-container logs: {"log":"Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behavior\n","stream":"stdout","time":"2017-01-24T06:12:51.468360646Z"} {"log":"Jan 24, 2017 6:12:52 AM hudson.remoting.jnlp.Main createEngine\n","stream":"stderr","time":"2017-01-24T06:12:52.078777831Z"} {"log":"INFO: Setting up slave: ecs-cloud-2b525d006ba\n","stream":"stderr","time":"2017-01-24T06:12:52.078797271Z"} {"log":"Jan 24, 2017 6:12:52 AM hudson.remoting.jnlp.Main$CuiListener \u003cinit\u003e\n","stream":"stderr","time":"2017-01-24T06:12:52.081422273Z"} {"log":"INFO: Jenkins agent is running in headless mode.\n","stream":"stderr","time":"2017-01-24T06:12:52.081434661Z"} {"log":"Jan 24, 2017 6:12:52 AM hudson.remoting.jnlp.Main$CuiListener status\n","stream":"stderr","time":"2017-01-24T06:12:52.118307707Z"} {"log":"INFO: Locating server among [http://52.53.170.100:8080/]\n","stream":"stderr","time":"2017-01-24T06:12:52.118328189Z"} {"log":"Jan 24, 2017 6:13:22 AM hudson.remoting.jnlp.Main$CuiListener error\n","stream":"stderr","time":"2017-01-24T06:13:22.169854689Z"} {"log":"SEVERE: Failed to connect to http://52.53.170.100:8080/tcpSlaveAgentListener/: connect timed
[JIRA] (JENKINS-41353) Unable to run ECS Slave for jenkins job
Title: Message Title rajasekaran radhakrishnan created an issue Jenkins / JENKINS-41353 Unable to run ECS Slave for jenkins job Issue Type: Bug Assignee: Nicolas De Loof Components: docker Created: 2017/Jan/24 5:58 AM Environment: ECS plugin Priority: Critical Reporter: rajasekaran radhakrishnan Hi Team, I am trying to run jenkins job with ECS Slave but it is showing your slave is offline. Steps to reproduce. Created ECS default cluster for slave. Created IAM role to give access to that cluster. Created jenkins master with IAM role to communicate with default ECS cluster. Configured ECS setup in jenkins configuration page. Fixed the TCP listen port for JNLP slaves of the Jenkins master (e.g. 5000) Started test job to print echo "hello world" it was not successful. My ECS-logs: [ec2-user@ip-172-31-44-102 ~]$ sudo tail -f /var/log/ecs/ecs-agent.log.2017-01-2 4-05 2017-01-24T05:28:03Z [INFO] Registering Instance with ECS 2017-01-24T05:28:04Z [INFO] Registered! module="api client" 2017-01-24T05:28:04Z [INFO] Registration completed successfully. I am running as 'arn:aws:ecs:us-east-1:274091617646:container-instance/096140a7-b534-446b-a2a3- 85e196cf697c' in cluster 'default' 2017-01-24T05:28:04Z [INFO] Saving state! module="statemanager" 2017-01-24T05:28:04Z [INFO] Beginning Polling for updates 2017-01-24T05:28:04Z [INFO] Event stream DeregisterContainerInstance start liste ning... 2017-01-24T05:28:04Z [INFO] Initializing stats engine 2017-01-24T05:28:04Z [INFO] Creating poll dialer, host: ecs-a-3.us-east-1.amazon aws.com 2017-01-24T05:28:04Z [INFO] Creating poll dialer, host: ecs-t-3.us-east-1.amazon aws.com 2017-01-24T05:28:14Z [INFO] Saving state! module="statemanager" 2017-01-24T05:39:04Z [INFO] Creating poll dialer, host: ecs-t-3.us-east-1.amazonaws.com
[JIRA] (JENKINS-41119) Not able to execute command on chef nodes parallely
Title: Message Title irfan sayed resolved as Fixed Code fixed. issue was related to data binding and wrong method name Jenkins / JENKINS-41119 Not able to execute command on chef nodes parallely Change By: irfan sayed 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
[JIRA] (JENKINS-41119) Not able to execute command on chef nodes parallely
Title: Message Title irfan sayed commented on JENKINS-41119 Re: Not able to execute command on chef nodes parallely This is fixed. closing now... 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-37597) ECS nodes not removed from build executor list
Title: Message Title Lee Webb commented on JENKINS-37597 Re: ECS nodes not removed from build executor list Hmm, this is interesting I updated to Jenkins 2.41 this morning, one of the 'enhancements' of which in that release is JNLP4 for all agents (https://issues.jenkins-ci.org/browse/JENKINS-40886) As soon as I updated any agents created by the ECS plugin were left in an idle state after their builds. I occasionally them go into a suspended state, but then they would come back out & go idle again. Because all the ECS cluster resources were in use, no more containers would spawn. Rolling back to 2.40 immediately corrected the issue. 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-40300) Support memoryReservation setting instead of memory for scheduling constraint
Title: Message Title Lee Webb closed an issue as Fixed Already merged Jenkins / JENKINS-40300 Support memoryReservation setting instead of memory for scheduling constraint Change By: Lee Webb 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-32018) Multibranch workflow project tracking multiple repositories
Title: Message Title Alastair D'Silva commented on JENKINS-32018 Re: Multibranch workflow project tracking multiple repositories This is a blocker for being able to evaluate the Blue Oceans plugin against various open source projects that we contribute to. I have a pull request here for evaluation, which allows for a user provided script via the config UI: https://github.com/jenkinsci/workflow-multibranch-plugin/pull/51 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-39985) Support context alert filters
Title: Message Title Goran Sarenkapa commented on JENKINS-39985 Re: Support context alert filters Excellent, my PC is currently undergoing repair. Thank you! I will take a look as soon as possible. I will be unable to test until i get it back. ETA is 7-14 business days according to Dell. 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-25587) Work items not included in build if work item number is not mentioned in the first line of a git commit
Title: Message Title
Lakshmi Narasimhan Vaikuntam updated an issue
Jenkins / JENKINS-25587
Work items not included in build if work item number is not mentioned in the first line of a git commit
Change By:
Lakshmi Narasimhan Vaikuntam
What steps will reproduce the problem?1. Create a git commit with multi line comment. Mention the work item number on the second line ( For eg, {{Sample git commit task ) 8 task 9 }} 2. In the Jenkins job, choose Rational Team Concert Git build step. Provide repository details. Select the following options. *Annotate Change log with work items links.* *Enable RTC Work Item Integration*2. Start a Jenkins job build .3. View the corresponding RTC Build Result work items task 7 and task 8 What is the expected output?The work item section 's links tab shows task as included in a link to the Jenkins buildWhat do you see instead? Please provide screen shots if possible.There are is no work items included Jenkins build link in the build Links tab of the work item Please provide any additional relevant information below (server logs, custom project area template, etc...).
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41133) Github Pull Requests showing up under Branches
Title: Message Title James Dumay commented on JENKINS-41133 Re: Github Pull Requests showing up under Branches Stewart Bryson unfortunately that would make things worse For more context read the description on JENKINS-41234 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-41193) Add log API for Org scanning and MBP indexing
Title: Message Title James Dumay edited a comment on JENKINS-41193 Re: Add log API for Org scanning and MBP indexing [~vivek] is it possible to also get the actual error that was thrown during Org Scanning or MBP indexing? I'd prefer if we could turn these into better error messages and only show the log if we fail to do that. (ping [~cliffmeyers] [~tfennelly]) 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-38668) ${CHANGES_SINCE_LAST_SUCCESS} no longer displays "No changes" when there are no new SCM changes
Title: Message Title
Alex Earl commented on JENKINS-38668
Re: ${CHANGES_SINCE_LAST_SUCCESS} no longer displays "No changes" when there are no new SCM changes
Are you still seeing this issue?
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-41193) Add log API for Org scanning and MBP indexing
Title: Message Title James Dumay commented on JENKINS-41193 Re: Add log API for Org scanning and MBP indexing Vivek Pandey is it possible to also get the actual error that was thrown during Org Scanning or MBP indexing? I'd prefer if we could turn these into better error messages and only show the log if we fail to do that. 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-38871) Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Undefined parameter var in token ENV], action = [Fail the build]
Title: Message Title Alex Earl commented on JENKINS-38871 Re: Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Undefined parameter var in token ENV], action = "" the build] I haven't been able to reproduce this...any update from your end if you have a more reproducible case? 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-41133) Github Pull Requests showing up under Branches
Title: Message Title Stewart Bryson commented on JENKINS-41133 Re: Github Pull Requests showing up under Branches James Dumay Does uninstalling and reinstalling the plugin possibly help? I saw some chatter that it's because of an upgrade that we applied. 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-40390) Publishing Fortify 360 FPR Data ERROR: Build step failed with exception java.lang.NumberFormatException: For input string: "0_72)"
Title: Message Title yogesh more commented on JENKINS-40390 Re: Publishing Fortify 360 FPR Data ERROR: Build step failed with exception java.lang.NumberFormatException: For input string: "0_72)" Hi, Is there any plan of fixing this for fortify 16.x versions? Thanks, Yogesh. 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-41341) Standardize form descriptions
Title: Message Title Brody Maclean commented on JENKINS-41341 Re: Standardize form descriptions https://zpl.io/Z20esxf 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-41341) Standardize form descriptions
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41341 Standardize form descriptions Change By: Brody Maclean Attachment: Modal Form.png 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-41133) Github Pull Requests showing up under Branches
Title: Message Title James Dumay commented on JENKINS-41133 Re: Github Pull Requests showing up under Branches I believe we need to release a new version of Blue Ocean that is compatible with SCM 2.0 API. We are working on making that available right now but I don't have an ETA just yet. 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-40326) Pipeline results (karaoke) doesn't reload when master is restarted
Title: Message Title Brody Maclean commented on JENKINS-40326 Re: Pipeline results (karaoke) doesn't reload when master is restarted https://zpl.io/23S6ep `rgba(0,0,0,0,25)` overlay div 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-40326) Pipeline results (karaoke) doesn't reload when master is restarted
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-40326 Pipeline results (karaoke) doesn't reload when master is restarted Change By: Brody Maclean Attachment: Connection Lost.png 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-41133) Github Pull Requests showing up under Branches
Title: Message Title Stewart Bryson commented on JENKINS-41133 Re: Github Pull Requests showing up under Branches Didn't help fo me. 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-41352) New dashboard cards
Title: Message Title
Brody Maclean commented on JENKINS-41352
Re: New dashboard cards
This is where I got to changing the CSS in the DOM. The icons are all a little off because the bounding boxes from the SVGs have been removed which makes them harder to resize & compare to the design. ``` .pipeline-card { padding: 8px 16px; } .favorites-card-stack .pipeline-card { margin-bottom: 8px; } .pipeline-card .actions { min-width: 100px; } .pipeline-card .actions > *:hover { color: #fff; opacity: .75; } .Favorite.dark-white:hover .star-filled { color: #fff } .pipeline-card .run > *, .pipeline-card .actions > * { margin-left: 8px; } .jdl-table.u-table-padding td:last-child, .jdl-table.u-table-padding th:last-child, .jdl-table td.u-table-padding:last-child, .jdl-table th.u-table-padding:last-child { padding-right: 16px; width: 40px; } ```
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-41352) New dashboard cards
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41352 New dashboard cards Change By: Brody Maclean Attachment: screenshot-1.png 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-41337) Jenkins Deploys all the projects irrespective of changed project
Title: Message Title sitaram makina updated an issue Jenkins / JENKINS-41337 Jenkins Deploys all the projects irrespective of changed project Change By: sitaram makina Priority: Minor Major 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-41352) New dashboard cards
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41352 New dashboard cards Change By: Michael Neale Sprint: pannonian 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-41352) New dashboard cards
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41352 New dashboard cards Issue Type: Story Assignee: Josh McDonald Components: blueocean-plugin Created: 2017/Jan/24 1:45 AM Priority: Major Reporter: Michael Neale The favourite card needs to be updated to reflect the new leaner design: Thinner Aligned elements Has last run information Follow on from: https://issues.jenkins-ci.org/browse/JENKINS-39341 (which is nearly ready) Add Comment
[JIRA] (JENKINS-41351) Access list of subversion checkin files in Jenkins ANT Script
Title: Message Title Sita Ram created an issue Jenkins / JENKINS-41351 Access list of subversion checkin files in Jenkins ANT Script Issue Type: Task Assignee: Unassigned Components: subversion-plugin Created: 2017/Jan/24 1:42 AM Environment: Jenkins, SVN are on Docker. Priority: Minor Reporter: Sita Ram Hi, I have deployed docker and have Jenkins and SVN running in it. I am trying to do a build with the the files that are checked into SVN. Setup Jenkins to poll the the SVN and it is succesfully polling and checking out those files into local copy. I now want to access the list of files that are part of the poll, so I can push those files to a server instead of pushing all. I can view the list of files from the build result but want to access that list from ANT script. Can someone help me on how to do this ? Thanks. Add Comment
[JIRA] (JENKINS-41339) Environment variables referencing other variables broken
Title: Message Title James Tatum edited a comment on JENKINS-41339 Re: Environment variables referencing other variables broken No envinject. This is a pretty vanilla Jenkins install, just pipeline and blue ocean. For fun, I created a digitalocean droplet, installed jenkins, and reproduced it. http://138.197.195.70:8080/ (L/P jenkinsbug:jenkinsbug) Did you setup the path in the right place? Mine is under Manage Jenkins > Configure System > Global Properties > Environment variables 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-41339) Environment variables referencing other variables broken
Title: Message Title James Tatum edited a comment on JENKINS-41339 Re: Environment variables referencing other variables broken No envinject. This is a pretty vanilla Jenkins install, just pipeline and blue ocean. For fun, I created a digitalocean droplet, installed jenkins, and reproduced it. http://138.197.195.70:8080/ Did you setup the path in the right place? Mine is under Manage Jenkins > Configure System > Global Properties > Environment variables 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-41339) Environment variables referencing other variables broken
Title: Message Title James Tatum edited a comment on JENKINS-41339 Re: Environment variables referencing other variables broken No envinject. This is a pretty vanilla Jenkins install, just pipeline and blue ocean. Here's the full list of For fun, I created a digitalocean droplet, installed plugins jenkins, and reproduced it. http : https: // gist 138 . github 197 . com 195.70:8080 / jtatum/3490869585f209b453ddc90ff85b7936 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-41339) Environment variables referencing other variables broken
Title: Message Title James Tatum commented on JENKINS-41339 Re: Environment variables referencing other variables broken No envinject. This is a pretty vanilla Jenkins install, just pipeline and blue ocean. Here's the full list of installed plugins: https://gist.github.com/jtatum/3490869585f209b453ddc90ff85b7936 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-41350) API to return full log for a stage or parallel branch
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41350 API to return full log for a stage or parallel branch Change By: Michael Neale Sprint: iapetus 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-41350) API to return full log for a stage or parallel branch
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41350 API to return full log for a stage or parallel branch Issue Type: Story Assignee: Vivek Pandey Components: blueocean-plugin Created: 2017/Jan/24 12:57 AM Priority: Minor Reporter: Michael Neale To support the UI, there is a need to fetch a rolled up log for a single stage (or parallel branch). This is not for streaming or tailing, but can be a simple aggregation of all step logs "contained" by the node/stage. Add Comment
[JIRA] (JENKINS-26583) Env-inject plugin suppress variables contributed by extension points
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26583 Re: Env-inject plugin suppress variables contributed by extension points Code changed in jenkins User: Nikolas Falco Path: src/main/java/jenkins/plugins/nodejs/NodeJSBuildWrapper.java src/main/java/jenkins/plugins/nodejs/NodeJSCommandInterpreter.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstallation.java src/main/java/jenkins/plugins/nodejs/tools/pathresolvers/FixEnvVarEnvironmentContributingAction.java http://jenkins-ci.org/commit/nodejs-plugin/06c1c1b56865bdf93dad79b5440e822ec680191b Log: Workaround for JENKINS-26583 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-41335) Allow variable to be defined within pipeline to be used in any stage
Title: Message Title Andrew Bayer commented on JENKINS-41335 Re: Allow variable to be defined within pipeline to be used in any stage Worth mentioning that in any scenario, the def would literally be redundant no matter what we're doing with the value - we wouldn't be literally calling this Groovy code at parse time, we'd be saying "Ok, here's the variable name, and here's what to set it to - evaluate that value at runtime and set the variable to that result". 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-41349) Post-FOSDEM 2017 Hackathon
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-41349 Post-FOSDEM 2017 Hackathon Issue Type: Epic Assignee: Kohsuke Kawaguchi Components: core, pipeline Created: 2017/Jan/24 12:32 AM Priority: Minor Reporter: R. Tyler Croy https://www.meetup.com/jenkinsmeetup/events/236370750/ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-26677) Blacklist certain classes from loading in slaves
Title: Message Title Liam Newman commented on JENKINS-26677 Re: Blacklist certain classes from loading in slaves How does this differ from JENKINS-38370, JENKINS-38371, etc? 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-41348) 'github' credentialId doesn't work when creating GitHub org folder
Title: Message Title Vivek Pandey commented on JENKINS-41348 Re: 'github' credentialId doesn't work when creating GitHub org folder Cliff MeyersGithubScmNavigator does lookup for credentials bit differently that how the 'github' credential is created by blueocean. So when GitHubScmNavigator does a lookup for 'github' credentialId, null is returned. Fix is in progress. 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-41348) 'github' credentialId doesn't work when creating GitHub org folder
Title: Message Title
Vivek Pandey created an issue
Jenkins / JENKINS-41348
'github' credentialId doesn't work when creating GitHub org folder
Issue Type:
Bug
Assignee:
Vivek Pandey
Components:
blueocean-plugin
Created:
2017/Jan/24 12:21 AM
Labels:
API
Priority:
Major
Reporter:
Vivek Pandey
As reported by Cliff Meyers: I've been working on the Github Creation API and have the first simplest flow wired up for creating an org folder. I am encountering a problem although I found the workaround for it. I wanted to run it by you to see what you think. First the UI calls this endpoint to get the credential that I previously created: http://localhost:8080/jenkins/blue/rest/organizations/jenkins/scm/github/ It returns an object like this (omitting _class and _links) { "credentialId": "github", "id": "github", "uri": "https://api.github.com" } Then I make a call to fetch the orgs which works fine: http://localhost:8080/jenkins/blue/rest/organizations/jenkins/scm/github/organizations/?credentialId=github Then when I make the creation call I send an object like this: { "name": "cliffmeyers", "$class": "io.jenkins.blueocean.blueocean_github_pipeline.GithubPipelineCreateRequest", "scmConfig": { "uri": "https://api.github.com", "config": { "orgName": "cliffmeyers", "repos": [] } } } This works fine. However if I add the credentialId: 'github' to this it fails saying invalid credential.
[JIRA] (JENKINS-41348) 'github' credentialId doesn't work when creating GitHub org folder
Title: Message Title Vivek Pandey started work on JENKINS-41348 Change By: Vivek Pandey Status: Open In Progress 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-41348) 'github' credentialId doesn't work when creating GitHub org folder
Title: Message Title
Vivek Pandey updated an issue
Jenkins / JENKINS-41348
'github' credentialId doesn't work when creating GitHub org folder
Change By:
Vivek Pandey
As reported by [~cliffmeyers]:I've been working on the Github Creation API and have the first simplest flow wired up for creating an org folder. I am encountering a problem although I found the workaround for it. I wanted to run it by you to see what you think.First the UI calls this endpoint to get the credential that I previously created:http://localhost:8080/jenkins/blue/rest/organizations/jenkins/scm/github/It returns an object like this (omitting _class and _links){ code} { "credentialId": "github","id": "github","uri": "https://api.github.com"} {code} Then I make a call to fetch the orgs which works fine:http://localhost:8080/jenkins/blue/rest/organizations/jenkins/scm/github/organizations/?credentialId=githubThen when I make the creation call I send an object like this: {code} {"name": "cliffmeyers","$class": "io.jenkins.blueocean.blueocean_github_pipeline.GithubPipelineCreateRequest","scmConfig": {"uri": "https://api.github.com","config": {"orgName": "cliffmeyers","repos": []}}} {code} This works fine. However if I add the credentialId: 'github' to this it fails saying invalid credential.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41347) Using JSON-Editor Returns Unformatted Json String
Title: Message Title
Taylor Christie created an issue
Jenkins / JENKINS-41347
Using JSON-Editor Returns Unformatted Json String
Issue Type:
Bug
Assignee:
vimil
Components:
extended-choice-parameter-plugin
Created:
2017/Jan/24 12:17 AM
Environment:
Jenkins 2.42
Labels:
plugin jenkins
Priority:
Minor
Reporter:
Taylor Christie
When attempting to use the Extended Choice plugin to export a json config to a file, it returns a string with no double quotes in it, rendering the json invalid. Build Log: Machine_Settings="{"containers":[{"hostname":"EDMCT","machine_template":"local:vztmpl/debian-jessie-custom.tar.gz","memory":512,"net":[ {"br":"vmbr1","dev":"eth0","gw":"192.168.15.1","ip":"dhcp","name":"net0","type":"veth","vlan":15} ],"node":"EDMHS0101","root_password":"asdasd","storage":"development-machines","storage_size":2,"swap":512}],"variable_host":"192.168.0.101"}"
Create a new container (on the ssh host) cd ~/playbooks export JSON=$ {Machine_Settings} echo $JSON > /tmp/create-lxc-instance.json
the /tmp/create-lxc-instance.json file: {containers:[{hostname:EDMCT,machine_template:local:vztmpl/debian-jessie-custom.tar.gz,memory:512,net:[ {br:vmbr1,dev:eth0,gw:192.168.15.1,ip:dhcp,name:net0,type:veth,vlan:15} ],node:EDMHS0101,root_password:asdasd,storage:development-machines,storage_size:2,swap:512}],variable_host:192.168.0.101} (The formatted data, but with no quotes so it is invalid json).
[JIRA] (JENKINS-41133) Github Pull Requests showing up under Branches
Title: Message Title Michael Neale commented on JENKINS-41133 Re: Github Pull Requests showing up under Branches hey Stewart Bryson can you try a "re-index" of jobs? (or did you already) as sometimes that is needed to update the metadata (at least for this release, I had to in some cases). 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-40820) Build time out does not work, I use abort the build
Title: Message Title ikedam commented on JENKINS-40820 Re: Build time out does not work, I use abort the build Ankit Gupta Please attach the job configuration file. It is located at $JENKINS_HOME/jobs/(Project name)/config.xml. Or a screenshot of the configuration page. Or let me know followings: The type of the job (freestyle, maven, ...) SCM (svn, git, ...) The configuration of build-timeout 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-41335) Allow variable to be defined within pipeline to be used in any stage
Title: Message Title
Robby Pocase commented on JENKINS-41335
Re: Allow variable to be defined within pipeline to be used in any stage
Not a huge fan of the redundant def either, but wanted a compromise to possibly allow script expressions. An alternative would be using _expression_ (similar to when) to be explicit about when script style usage is allowed. I'm not overly fond of this syntax either, but it does provide some consistency with other declarative constructs.
define {
my_var = _expression_ { return "foo" == "bar" }
}
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-40820) Build time out does not work, I use abort the build
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-40820 Build time out does not work, I use abort the build Change By: ikedam Assignee: Kohsuke Kawaguchi ikedam 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-41274) "Run as Specific User" does not work with Pipeline Jobs
Title: Message Title ikedam assigned an issue to Jason Swager Let me know more details. If "Run as Specific User" doesn't work, the build should run as the system user, and it sounds strange that it run as the user that ran the job. How did you see that the build ran as that user? (from the console output?) Jenkins / JENKINS-41274 "Run as Specific User" does not work with Pipeline Jobs Change By: ikedam Assignee: Jason Swager 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-40734) Shell step cannot use environment variables that contain $$
Title: Message Title
John Ericson edited a comment on JENKINS-40734
Re: Shell step cannot use environment variables that contain $$
I think this is a rather glaring breaking change? I and others on IRC did things like set a global custom PATH "extension", redefining path as {{$PATH:/some/other/fallback}}. This now breaks and {{$PATH}} is not expanded. The aforementioned double-quote solution seems to work fine---I'd be very happy if this PR was reverted and a new commit made to restore comparability. The old way is strictly more expressive, as one can, worse case (and not required for this example), escape the env var definition manually.
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-40734) Shell step cannot use environment variables that contain $$
Title: Message Title
John Ericson edited a comment on JENKINS-40734
Re: Shell step cannot use environment variables that contain $$
I think this is a rather glaring breaking change? I and others on IRC did things like set a global custom PATH "extension", redefining path as ` {{ $PATH:/some/other/fallback ` }} . This now breaks and {{$PATH}} is not expanded.
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-40734) Shell step cannot use environment variables that contain $$
Title: Message Title John Ericson commented on JENKINS-40734 Re: Shell step cannot use environment variables that contain $$ I think this is a rather glaring breaking change? I and others on IRC did things like set a global custom PATH "extension", redefining path as `$PATH:/some/other/fallback`. 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-39810) Jenkins can't connect to any HTTP sites for plug-ins, complains about 403 error
Title: Message Title ikedam commented on JENKINS-39810 Re: Jenkins can't connect to any HTTP sites for plug-ins, complains about 403 error Jenkins itself doesn't seem provide a feature to set the user agent (e.g. as a configuration field in GUI). JVM provides a system property "http.agent" to set the useragent string. I haven't tested it, but would you try that and see it takes effect? 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-41185) [Declarative Pipeline] Stage "when" should have logical operator steps (and, or, not, all, any)
Title: Message Title Andrew Bayer commented on JENKINS-41185 Re: [Declarative Pipeline] Stage "when" should have logical operator steps (and, or, not, all, any) Starting preliminary work on this, but it won't land 'til post-1.0. 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-41185) [Declarative Pipeline] Stage "when" should have logical operator steps (and, or, not, all, any)
Title: Message Title Andrew Bayer started work on JENKINS-41185 Change By: Andrew Bayer Status: Open In Progress 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-41333) Multi-branch pipeline support stopped working
Title: Message Title Oleg Nenashev commented on JENKINS-41333 Re: Multi-branch pipeline support stopped working Will check it in a couple of weeks. Have no access to the laptop now (vacation). Please provide the list of Pipeline plugin versions. From which Jenkins version have you also upgraded? 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-41146) SCM Trigger configuration being overwritten by SYSTEM user in Pipeline
Title: Message Title Andrew Bayer commented on JENKINS-41146 Re: SCM Trigger configuration being overwritten by SYSTEM user in Pipeline Yup, that's, for good or for ill, by design. If you check your build's logs, you'll see it warning you that you're overwriting your properties. 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-39810) Jenkins can't connect to any HTTP sites for plug-ins, complains about 403 error
Title: Message Title ikedam assigned an issue to Danny Chia Jenkins / JENKINS-39810 Jenkins can't connect to any HTTP sites for plug-ins, complains about 403 error Change By: ikedam Assignee: Danny Chia 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-41191) read-only artifact files and build slaves
Title: Message Title Andrew Johnson closed an issue as Cannot Reproduce Not a bug according to the maintainer, easily worked around. Jenkins / JENKINS-41191 read-only artifact files and build slaves Change By: Andrew Johnson Status: Resolved Closed 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-41191) read-only artifact files and build slaves
Title: Message Title Andrew Johnson commented on JENKINS-41191 Re: read-only artifact files and build slaves Presumably the behavior on the master has been fixed in a newer version of Jenkins than we're currently running. It still seems weird to me though that an upstream job can break downstream jobs that use this plugin merely by changing the permission of the files that it provides as artifacts. The permissions of the artifact files are not visible anywhere in the Jenkins GUI that I can see, so there's no easy way for a downstream job's author to know in advance whether they have to allow for this or not. This is obviously trivial to fix in a build script or with some other plugin so it's not really a problem once you realize what's causing the failure, just slightly annoying. Thanks anyway - Andrew 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-41339) Environment variables referencing other variables broken
Title: Message Title
Daniel Beck edited a comment on JENKINS-41339
Re: Environment variables referencing other variables broken
Cannot reproduce on a pristine installation of Jenkins 2. 0 40 with current releases of Pipeline and its dependencies (installed 10 minutes ago) .{noformat}Started by user admin[Pipeline] nodeRunning on master in /Users/danielbeck/JENKINS-41339-Home/workspace/pipe[Pipeline] {[Pipeline] echoenv.PATH=/Users/danielbeck/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/groovy/bin:/opt/X11/bin:/usr/local/MacGPG2/bin[Pipeline] sh[pipe] Running shell script+ env…{noformat}Let me guess, envinject is installed and you're doing something insane like undefining all node environment variables?
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-41339) Environment variables referencing other variables broken
Title: Message Title
Daniel Beck commented on JENKINS-41339
Re: Environment variables referencing other variables broken
Cannot reproduce on a pristine installation of Jenkins 2.0.
Started by user admin
[Pipeline] node
Running on master in /Users/danielbeck/JENKINS-41339-Home/workspace/pipe
[Pipeline] {
[Pipeline] echo
env.PATH=/Users/danielbeck/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/groovy/bin:/opt/X11/bin:/usr/local/MacGPG2/bin
[Pipeline] sh
[pipe] Running shell script
+ env
…
Let me guess, envinject is installed and you're doing something insane like undefining all node environment variables?
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-40852) Integrate the sheet component into the editor
Title: Message Title Keith Zantow updated JENKINS-40852 Jenkins / JENKINS-40852 Integrate the sheet component into the editor Change By: Keith Zantow Status: In Progress Review 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-40852) Integrate the sheet component into the editor
Title: Message Title Keith Zantow started work on JENKINS-40852 Change By: Keith Zantow Status: Open In Progress 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-40852) Integrate the sheet component into the editor
Title: Message Title Keith Zantow assigned an issue to Keith Zantow Jenkins / JENKINS-40852 Integrate the sheet component into the editor Change By: Keith Zantow Assignee: Josh McDonald Keith Zantow 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-41339) Environment variables referencing other variables broken
Title: Message Title Andrew Bayer assigned an issue to Jesse Glick Jenkins / JENKINS-41339 Environment variables referencing other variables broken Change By: Andrew Bayer Assignee: Jesse Glick 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-41346) Validate and show errors at location
Title: Message Title Keith Zantow updated an issue Jenkins / JENKINS-41346 Validate and show errors at location Change By: Keith Zantow Sprint: pannonian 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-41346) Validate and show errors at location
Title: Message Title Keith Zantow started work on JENKINS-41346 Change By: Keith Zantow Status: Open In Progress 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-41346) Validate and show errors at location
Title: Message Title Keith Zantow created an issue Jenkins / JENKINS-41346 Validate and show errors at location Issue Type: Improvement Assignee: Keith Zantow Components: blueocean-pipeline-editor-plugin Created: 2017/Jan/23 10:46 PM Priority: Critical Reporter: Keith Zantow Instead of getting random, difficult to decipher errors in a single dialog error message when attempting to "save" (aka. convert a pipeline from json), use the location to find the appropriate locations in the UI to show errors to the user, also validate multiple times as the user is editing things, and ensure required fields are filled out. Add Comment
[JIRA] (JENKINS-41323) Do not throw exception during hash computation if source code is not available
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-41323 Do not throw exception during hash computation if source code is not available Change By: Ulli Hafner Summary: Make it possible to parse XML report without access to Do not throw exception during hash computation if source code is not available Component/s: analysis-core-plugin Component/s: dry-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41323) Make it possible to parse XML report without access to source code
Title: Message Title Ulli Hafner commented on JENKINS-41323 Re: Make it possible to parse XML report without access to source code I think it should not harm if I replace the exception with a logging statement (or ignore it anyway). The error will show up anyway when you click into the source code view that should visualize the warning (not as exception but as a error message in the view). Note that without source files the detection of new and fixed warnings will not work well. 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-39810) Jenkins can't connect to any HTTP sites for plug-ins, complains about 403 error
Title: Message Title ikedam updated an issue Jenkins / JENKINS-39810 Jenkins can't connect to any HTTP sites for plug-ins, complains about 403 error Sounds not related to updatesite-manager plugin. Change By: ikedam Component/s: core Component/s: update-sites-manager-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-41345) P4 Plugin does not read credentials from folders
Title: Message Title Clifford Holden commented on JENKINS-41345 Re: P4 Plugin does not read credentials from folders FolderGlobal shows the credentials available in the folder global space. The standard credential is there, and is accessible by the Subversion plugin. TopGlobal shows the perforce credential in the Jenkins/Global store, but with the SDB Domain . The configuration page for the VE03FW project (OnlySelected) only shows the credential in the Jenkins Store, not the folder store. As I understand how this works, all users will have access to the Jenkins Global store, and can use those credentials. This is a problem in that if we have several groups using the server, they will need to have separate perforce credentials for each group that are not shared between them. 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-41345) P4 Plugin does not read credentials from folders
Title: Message Title Clifford Holden updated an issue Jenkins / JENKINS-41345 P4 Plugin does not read credentials from folders Change By: Clifford Holden Attachment: OnlySelected.PNG Attachment: TopGlobal.PNG Attachment: FolderGlobal.PNG 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-41303) Managed Files does not list previous config file after update
Title: Message Title Anil Belur commented on JENKINS-41303 Re: Managed Files does not list previous config file after update You can still add new config files which does not show up on the list. 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-40939) Naginator plugin and regex
Title: Message Title ikedam commented on JENKINS-40939 Re: Naginator plugin and regex I can't get what you mean, but that's apparent from the implementation and unittests of the plugin. I conclude it's not a bug as a maintainer and don't fix it. 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-40596) 400 upon opening direct link of project in a GitHub organization project
Title: Message Title Daniel Beck commented on JENKINS-40596 Re: 400 upon opening direct link of project in a GitHub organization project The rev proxy mon issue is tracked as JENKINS-31068. 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-41345) P4 Plugin does not read credentials from folders
Title: Message Title Clifford Holden created an issue Jenkins / JENKINS-41345 P4 Plugin does not read credentials from folders Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2017/Jan/23 10:30 PM Environment: Ubuntu 15.10 Jenkins ver. 2.32.1 Updated P4 Plugin and Credential Plugin as of 1/12/17 Firefox Priority: Major Reporter: Clifford Holden When putting credentials into a Folder credential store the P4 credentials cannot be "seen" by the jobs in the same folder. They have to be in the Global store to be seen. The P4 plugin says "P4 Plugin credentials must be added to the Global or a user defined domain, using one of the two supported Credentials: 'Perforce Password Credential' or 'Perforce Ticket Credential'." (Emphasis Mine) We need to have selective control of credentials per folder. This works for Subversion, but not for P4. Add Comment
[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project
Title: Message Title James Dumay resolved as Not A Defect Unfortunately the way we URL encode things like branch names and organization names you do have to make this config change to Tomcat for it to work correctly. Tomcat isn't the recommended way of deploying Jenkins and most people use Jetty. Jenkins / JENKINS-40596 400 upon opening direct link of project in a GitHub organization project Change By: James Dumay Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-41091) git-parameter:0.7.1 breaks the multi-line parameters in rebuild
Title: Message Title Michal Kowalski commented on JENKINS-41091 Re: git-parameter:0.7.1 breaks the multi-line parameters in rebuild Thanks a lot Boguslaw Klimas! 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-41341) Standardize form descriptions
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41341 Standardize form descriptions Change By: James Dumay *In Scope** Form elements should come with a way of providing a description* Description should appear between the element label and value.* Update the job parameter dialog so that it uses the form element description. * The primary button should be first That means a form input should be displayed in this order:* Label* Description* Value (radios, checkbox, etc) 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-41341) Standardize form descriptions
Title: Message Title Brody Maclean commented on JENKINS-41341 Re: Standardize form descriptions Primary button first. Labels seem out of order and too tight. 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-41341) Standardize form descriptions
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41341 Standardize form descriptions Change By: Brody Maclean Attachment: screenshot-1.png 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-39664) Docker builds do not work with Kubernetes Pipeline plugin
Title: Message Title Roman Safronov commented on JENKINS-39664 Re: Docker builds do not work with Kubernetes Pipeline plugin Same issue with kubernetes-plugin 0.10. docker.build "myimage" fails, but if i replace it to sh 'docker build -t myimage .' it works. 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-40466) Developer wants to see a message when Jenkins is busy eg: execution is blocked waiting for a node
Title: Message Title Vivek Pandey updated JENKINS-40466 Jenkins / JENKINS-40466 Developer wants to see a message when Jenkins is busy eg: execution is blocked waiting for a node Change By: Vivek Pandey Status: In Review 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] (JENKINS-41282) Time ago "A few seconds" should be more precise
Title: Message Title James Dumay assigned an issue to Thorsten Scherler Jenkins / JENKINS-41282 Time ago "A few seconds" should be more precise Change By: James Dumay Assignee: Thorsten Scherler 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-41282) Time ago "A few seconds" should be more precise
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41282 Time ago "A few seconds" should be more precise Change By: James Dumay Sprint: iapetus pannonian 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-41341) Standardize form descriptions
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41341 Standardize form descriptions Change By: James Dumay *In Scope** Form elements should come with a way of providing a description* Description should appear between the element label and value.* Update the job parameter dialog so that it uses the form element description. That means a form input should be displayed in this order:* Label* Description* Value (radios, checkbox, etc) 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.
