[JIRA] (JENKINS-50932) `hostPort` only works for one pod at a time
Title: Message Title Juha Tiensyrjä commented on JENKINS-50932 Re: `hostPort` only works for one pod at a time I attached `clitest-rcc-pods-1.3.3` to show how all the pods have host ports when running with Kubernetes plugin 1.3.3. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50932) `hostPort` only works for one pod at a time
Title: Message Title
Juha Tiensyrjä created an issue
Jenkins / JENKINS-50932
`hostPort` only works for one pod at a time
Issue Type:
Bug
Assignee:
Carlos Sanchez
Attachments:
clitest-rcc-pods
Components:
kubernetes-plugin
Created:
2018-04-23 06:40
Labels:
regression
Priority:
Major
Reporter:
Juha Tiensyrjä
We are running tests against our environments with a test container and a callback container for the tests in the same pod. The callback container has a hostPort defined to receive the callbacks from the services to be tested. Kubernetes plugin up until version 1.3.3 works with our setup, but starting from 1.4.0 it looks like only one of the three pods running in parallel actually manages to get that hostPort, the other two don't. The pod definition we are using in the pipeline script looks like this:
podTemplate(
name: podName,
label: podName,
instanceCap: 1,
containers: [
containerTemplate(
name: 'clitest',
image: "private-docker-repo/platform/clitest:${clitestVersion}",
command: 'cat',
ttyEnabled: true,
resourceRequestCpu: '500m',
resourceLimitCpu: '2000m',
resourceRequestMemory: '1000Mi',
resourceLimitMemory: '1000Mi',
),
containerTemplate(
name: 'rcc',
image: 'private-docker-repo/platform/rcc:0.2',
command: '/bin/bash',
args: '-c "/opt/rcc/start.sh `wget -q -O -
[JIRA] (JENKINS-50932) `hostPort` only works for one pod at a time
Title: Message Title Juha Tiensyrjä updated an issue Jenkins / JENKINS-50932 `hostPort` only works for one pod at a time Change By: Juha Tiensyrjä Attachment: clitest-rcc-pods Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50932) `hostPort` only works for one pod at a time
Title: Message Title Juha Tiensyrjä updated an issue Jenkins / JENKINS-50932 `hostPort` only works for one pod at a time Change By: Juha Tiensyrjä Attachment: clitest-rcc-pods Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50933) Create Jenkins/Remoting integration testing flow
Title: Message Title Oleg Nenashev started work on JENKINS-50933 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50933) Create Jenkins/Remoting integration testing flow
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50933 Create Jenkins/Remoting integration testing flow Issue Type: Task Assignee: Oleg Nenashev Components: remoting Created: 2018-04-23 07:21 Labels: essentials Priority: Minor Reporter: Oleg Nenashev Currently Remoting has not Jenkins integration tests in the repository. It would be great to run a subset of tests in Remoting PR builder, including Jenkins Core JTH, Plugin PCT and ATH Add Comment
[JIRA] (JENKINS-50934) Triggered builds "for every property file" do not receive the parameters from the property files
Title: Message Title
Alexandru Băluț created an issue
Jenkins / JENKINS-50934
Triggered builds "for every property file" do not receive the parameters from the property files
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Screen Shot 2018-04-19 at 15.35.35.png
Components:
parameterized-trigger-plugin
Created:
2018-04-23 07:29
Environment:
Jenkins ver. 2.107.1 Parameterized Trigger plugin 2.35.2
Priority:
Minor
Reporter:
Alexandru Băluț
I set up job A which has a single Trigger/call builds on other projects build step which can be seen in the attached screenshot. It's set For every property file, invoke one build of job B. The File Pattern is /var/lib/jenkins/cases/* Job B ("case-runner" in the screenshot) is parameterized, it has a DATASET parameter and a single build step Execute shell "env". It is started as expected, but the DATASET parameter is not passed through even though it's specified in the property file. jenkins@instance-eval-jenkins:~$ ls -l /var/lib/jenkins/cases/ total 4 rw-rr- 1 jenkins jenkins 12 Apr 19 13:08 a jenkins@instance-eval-jenkins:~$ cat /var/lib/jenkins/cases/a DATASET=svo The DATASET parameter should be passed through according to the documentation: "This ParameterFactory generates parameters based on the contents of the files found." DATASET is passed fine if I specify it in a list of Predefined parameters, but not when it's in the property file, so it seems to be a problem with how the job is triggered. Both jobs run on the master Jenkins node. I also tried with "DATASET = svo" in the property file but still the same.
[JIRA] (JENKINS-50837) [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3
Title: Message Title Saheta B commented on JENKINS-50837 Re: [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3 Hi, Any update on this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50932) `hostPort` only works for one pod at a time
Title: Message Title Juha Tiensyrjä updated an issue Jenkins / JENKINS-50932 `hostPort` only works for one pod at a time Change By: Juha Tiensyrjä Attachment: clitest-rcc-pods-1.3.3 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50916) Add support for JUnit health factor configuration attribute
Title: Message Title Cyrille Le Clerc updated JENKINS-50916 Jenkins / JENKINS-50916 Add support for JUnit health factor configuration attribute Change By: Cyrille Le Clerc Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50916) Add support for JUnit health factor configuration attribute
Title: Message Title Cyrille Le Clerc started work on JENKINS-50916 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50434) Misbehaviour of feature: Pin the workspace to the build host
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-50434 Misbehaviour of feature: Pin the workspace to the build host Change By: Paul Allen Labels: P4_VERIFY P4_A Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title
Hugh Saunders edited a comment on JENKINS-48061
Re: git plugin 3.6.4 regression with shared libraries
Hey [~markewaite], I built [~rsandell]'s branch at 887ac3394c48e844147de591277a0457adb345a3 but it didn't solve my problem. Version:{code:java}Git pluginThis plugin integrates Git with Jenkins.3.8.1-SNAPSHOT (private-887ac339-hughsaunders) Downgrade to 3.6.3{code}Console:{code:java}GitHub pull request #719 of commit f35de294eaebcbe5aecd824b444d1d901777814a, no merge conflicts.Setting status of f35de294eaebcbe5aecd824b444d1d901777814a to PENDING with url https://rpc.jenkins.cit.rackspace.net/job/RPC-Pull-Request-Issue-Link_rpc_gating/1806/ and message: 'Build started sha1 is merged.'Using context: CIT/issue-linkRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] libraryLoading library rpc-gating@origin/pr/719/mergeAttempting to resolve origin/pr/719/merge from remote references... > git --version # timeout=10using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc > git ls-remote -h https://github.com/rcbops/rpc-gating.git # timeout=10Could not find origin/pr/719/merge in remote references. Pulling heads to local for deep search... > git rev-parse --is-inside-work-tree # timeout=10Setting origin to https://github.com/rcbops/rpc-gating.git > git config remote.origin.url https://github.com/rcbops/rpc-gating.git # timeout=10Fetching origin...Fetching upstream changes from origin > git --version # timeout=10using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/heads/origin/pr/* > git rev-parse origin/pr/719/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains 10939c10d74f2284e1078a7371d49587d71858a1 # timeout=10Could not find a branch containing commit 10939c10d74f2284e1078a7371d49587d71858a1[Pipeline] End of Pipeline[BFA] Scanning build for known causes...[BFA] No failure causes found[BFA] Done. 0sSetting status of f35de294eaebcbe5aecd824b444d1d901777814a to FAILURE with url https://rpc.jenkins.cit.rackspace.net/job/RPC-Pull-Request-Issue-Link_rpc_gating/1806/ and message: 'Build finished. 'Using context: CIT/issue-linkERROR: No version origin/pr/719/merge found for library rpc-gatingFinished: FAILURE{code}Its frustrating because the ref is obviously valid as{code:java} git rev-parse origin/pr/719/merge^{commit}{code}successfully translates it to a SHA. As before, when running the commands manually, a branch is found:{code:java}10:08 $ git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/heads/origin/pr/*remote: Counting objects: 1319, done.remote: Compressing objects: 100% (12/12), done.remote: Total 1319 (delta 755), reused 753 (delta 752), pack-reused 555Receiving objects: 100% (1319/1319), 232.31 KiB | 1.40 MiB/s, done.Resolving deltas: 100% (830/830), completed with 453 local objects.From github.com:rcbops/rpc-gating* [new ref] refs/pull/1/head -> origin/pr/1/head* [new ref] refs/pull/10/head -> origin/pr/10/head* [new ref] refs/pull/100/head -> origin/pr/100/head...10:08 $ git branch -a -v --no-abbrev --contains 10939c10d74f2284e1078a7371d49587d71858a1origin/pr/719/merge 10939c10d74f2284e1078a7371d49587d71858a1 Merge f35de294eaebcbe5aecd824b444d1d901777814a into b0359387d639b5d7df8267f4fa09c0bba798a286{code}
[JIRA] (JENKINS-44860) Disable masking of usernames
Title: Message Title
Oliver Lockwood edited a comment on JENKINS-44860
Re: Disable masking of usernames
We came across this issue last week as well and, having discovered this issue, are contemplating contributing a fix.Just to be clear, we'd like to: * use the username/password credentials type * use the following pipeline script to provide username and password as environment variables to the pipeline script closure and e.g. any shell commands within it: ** {noformat}withCredentials([usernamePassword(credentialsId: 'MY_CRED_ID', usernameVariable: 'USER_ENV_VAR', passwordVariable: 'PASSWORD_ENV_VAR')]) { ... }{noformat} * have any instances of whatever the password is be masked in console output * NOT have any instances of whatever the username is masked in console output.This would then correlate correctly with the view on the {{jenkinsUrl/credentials}} page, which shows {{user-name/** (description)}} in the {{Name}} column for credentials of this type.[~jglick] we already found the {{UsernamePasswordMultiBinding}} class; but it looks to us (perhaps naively?) that the return value of the `bind()` method is used in {{BindingStep.Execution.start()}} *both* for actually providing the environment variables (through the use of {{EnvironmentExpander}}) *and* for obfuscating the secrets into {{}} (through the use of {{Filter}}). So it's not clear to me how the patch you're suggesting would allow us to still provide the username from a Credential without it being obfuscated. Have I misunderstood your comment? Many thanks.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received
[JIRA] (JENKINS-44860) Disable masking of usernames
Title: Message Title
Oliver Lockwood edited a comment on JENKINS-44860
Re: Disable masking of usernames
We came across this issue last week as well and, having discovered this issue, are contemplating contributing a fix.Just to be clear, we'd like to: * use the username/password credentials type * use the following pipeline script to provide username and password as environment variables to the pipeline script closure and e.g. any shell commands within it: ** {noformat}withCredentials([usernamePassword(credentialsId: 'MY_CRED_ID', usernameVariable: 'USER_ENV_VAR', passwordVariable: 'PASSWORD_ENV_VAR')]) { ... }{noformat} * have any instances of whatever the password is be masked in console output * NOT have any instances of whatever the username is masked in console output.This would then correlate correctly with the view on the {{jenkinsUrl/credentials}} page, which shows {{user-name/** (description)}} in the {{Name}} column for credentials of this type.[~jglick] we already found the {{UsernamePasswordMultiBinding}} class; but it looks to us (perhaps naively?) that the return value of the `bind()` method is used in {{BindingStep.Execution.start()}} *both* for actually providing the environment variables (through the use of {{EnvironmentExpander}}) *and* for obfuscating the secrets into {{}} (through the use of {{Filter}}). So it's not clear to me how the patch you're suggesting would allow us to still provide the username from a Credential without it being obfuscated. Have I misunderstood your comment? Many thanks.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You
[JIRA] (JENKINS-50935) All jobs executing SonarQube Scanner lost server related vars after plugin upgrade to 2.7.1
Title: Message Title Alexandre Aubert created an issue Jenkins / JENKINS-50935 All jobs executing SonarQube Scanner lost server related vars after plugin upgrade to 2.7.1 Issue Type: Bug Assignee: Sonar Team Components: sonar Created: 2018-04-23 08:57 Environment: jenkins LTS 2.107.2 sonarqube scanner 2.7.1 Labels: sonar-plugin sonarqube sonar Priority: Blocker Reporter: Alexandre Aubert After upgrade of sonarqube scanner plugin from 2.6.1 to 2.7.1, all jobs with sonar step configured have lost the link with 'Sonar server' configured in Jenkins > Manage > configure System > SonarQube servers. Then, token used to contact API is no more loaded during job execution and step fails with 'Not authorized' error from Sonar. When checking each job configuration, there is indeed no more 'server' choice dropdown in configuration step. This is a really annoying regression, as we have a lot of jobs that suffers from that. Workaround of adding credentials for each job is not really an option, as we have really a large impact. Thanks for your help on that.
[JIRA] (JENKINS-50838) The plugin doesn't login anymore
Title: Message Title Rafal Janicki commented on JENKINS-50838 Re: The plugin doesn't login anymore Sorry, I think I'm using a wrong naming. I mean the version that's hosted on gitlab.com (SaaS), not self-hosted Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-44860) Disable masking of usernames
Title: Message Title
Oliver Lockwood commented on JENKINS-44860
Re: Disable masking of usernames
We came across this issue last week as well and, having discovered this issue, are contemplating contributing a fix. Just to be clear, we'd like to:
use the username/password credentials type
use the pipeline script {{withCredentials([usernamePassword(credentialsId: 'MY_CRED_ID', usernameVariable: 'USER_ENV_VAR', passwordVariable: 'PASSWORD_ENV_VAR')]) { ... }}} to provide username and password as environment variables to the pipeline script closure and e.g. any shell commands within it
have any instances of whatever the password is be masked in console output
NOT have any instances of whatever the username is masked in console output.
This would then correlate correctly with the view on the jenkinsUrl/credentials page, which shows user-name/** (description) in the Name column for credentials of this type. Jesse Glick we already found the UsernamePasswordMultiBinding class; but it looks to us (perhaps naively?) that the return value of the `bind()` method is used in BindingStep.Execution.start() both for actually providing the environment variables (through the use of EnvironmentExpander) and for obfuscating the secrets into (through the use of Filter). So it's not clear to me how the patch you're suggesting would allow us to still provide the username from a Credential without it being obfuscated. Have I misunderstood your comment? Many thanks.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50937) GitHub Multibranch PR: unclear error message for PR with merge conflicts
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-50937 GitHub Multibranch PR: unclear error message for PR with merge conflicts Issue Type: Improvement Assignee: Unassigned Attachments: image-2018-04-23-11-50-14-833.png Components: pipeline Created: 2018-04-23 09:51 Environment: Jenkins: 2.107.2 Declarative Pipeline: 1.2.9 Blue Ocean: 1.5.0 Git Plugin: 3.8.0 https://github.com/cyrille-leclerc/my-spring-boot-app/pull/1 Priority: Minor Reporter: Cyrille Le Clerc When there is a merge conflict on a GitHub PR, Jenkins displays a cryptic exception instead of having a clear message with an hyperlink to the pull request on github. Branch indexing Connecting to https://api.github.com using admin/** (GitHub Access Token) Checking out git https://github.com/cyrille-leclerc/my-spring-boot-app.git into /opt/jenkins-oss/jenkins_home/workspace/my-spring-boot-app_PR-1-DZVOWEKBTG4QNQLVIUGZDZT4OEREYWOQPQSIZTLS3MU4M6ZJ5Q3A@script to read Jenkinsfile Cloning the remote Git repository Cloning with configured refspecs honoured and without tags Cloning repository https://github.com/cyrille-leclerc/my-spring-boot-app.git > git init /opt/jenkins-oss/jenkins_home/workspace/my-spring-boot-app_PR-1-DZVOWEKBTG4QNQLVIUGZDZT4OEREYWOQPQSIZTLS3MU4M6ZJ5Q3A@script # timeout=10 Fetching upstream changes from https://github.com/cyrille-leclerc/my-spring-boot-app.git > git
[JIRA] (JENKINS-50204) Visualization of the credentials backed by Kubernetes secrets in Jenkins Credentials UI
Title: Message Title Steve Arch closed an issue as Done Jenkins / JENKINS-50204 Visualization of the credentials backed by Kubernetes secrets in Jenkins Credentials UI Change By: Steve Arch Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title Adrian David started work on JENKINS-49033 Change By: Adrian David Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50838) The plugin doesn't login anymore
Title: Message Title Thibaud Lepretre commented on JENKINS-50838 Re: The plugin doesn't login anymore Are you using GitLab 10.7? I'm asking because since GitLab 10.7 I have issue with Jenkins GitLab Oauth plugin I have infinite redirection (because I think in my use case I'm have policy that force user to be logged, there is no public access even read-only). With GitLab 10.6 I had no issues. I think my issue should be the same as yours if you're using GitLab 10.7. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50838) The plugin doesn't login anymore
Title: Message Title Rafal Janicki commented on JENKINS-50838 Re: The plugin doesn't login anymore No, I'm using the hosted version, not the EE. But I guess it's up to date Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50936) How to get all the packages and its coverage by api
Title: Message Title Lieping Xie created an issue Jenkins / JENKINS-50936 How to get all the packages and its coverage by api Issue Type: New Feature Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2018-04-23 09:28 Priority: Major Reporter: Lieping Xie There is api to get the summary coverage report, but there is no such api to get all the packages and its corresponding coverage data, can it be supported? Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-44860) Disable masking of usernames
Title: Message Title
Oliver Lockwood edited a comment on JENKINS-44860
Re: Disable masking of usernames
We came across this issue last week as well and, having discovered this issue, are contemplating contributing a fix.Just to be clear, we'd like to: * use the username/password credentials type * use the following pipeline script to provide username and password as environment variables to the pipeline script closure and e.g. any shell commands within it: **{noformat}withCredentials([usernamePassword(credentialsId: 'MY_CRED_ID', usernameVariable: 'USER_ENV_VAR', passwordVariable: 'PASSWORD_ENV_VAR')]) { ... }{noformat} * have any instances of whatever the password is be masked in console output * NOT have any instances of whatever the username is masked in console output.This would then correlate correctly with the view on the {{jenkinsUrl/credentials}} page, which shows {{user-name/** (description)}} in the {{Name}} column for credentials of this type.[~jglick] we already found the {{UsernamePasswordMultiBinding}} class; but it looks to us (perhaps naively?) that the return value of the `bind()` method is used in {{BindingStep.Execution.start()}} *both* for actually providing the environment variables (through the use of {{EnvironmentExpander}}) *and* for obfuscating the secrets into {{}} (through the use of {{Filter}}). So it's not clear to me how the patch you're suggesting would allow us to still provide the username from a Credential without it being obfuscated. Have I misunderstood your comment? Many thanks.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message
[JIRA] (JENKINS-44860) Disable masking of usernames
Title: Message Title
Oliver Lockwood edited a comment on JENKINS-44860
Re: Disable masking of usernames
We came across this issue last week as well and, having discovered this issue, are contemplating contributing a fix.Just to be clear, we'd like to: * use the username/password credentials type * use the following pipeline script to provide username and password as environment variables to the pipeline script closure and e.g. any shell commands within it: ** { { noformat} withCredentials([usernamePassword(credentialsId: 'MY_CRED_ID', usernameVariable: 'USER_ENV_VAR', passwordVariable: 'PASSWORD_ENV_VAR')]) \ { ... } {noformat } } * have any instances of whatever the password is be masked in console output * NOT have any instances of whatever the username is masked in console output.This would then correlate correctly with the view on the {{jenkinsUrl/credentials}} page, which shows {{user-name/** (description)}} in the {{Name}} column for credentials of this type.[~jglick] we already found the {{UsernamePasswordMultiBinding}} class; but it looks to us (perhaps naively?) that the return value of the `bind()` method is used in {{BindingStep.Execution.start()}} *both* for actually providing the environment variables (through the use of {{EnvironmentExpander}}) *and* for obfuscating the secrets into {{}} (through the use of {{Filter}}). So it's not clear to me how the patch you're suggesting would allow us to still provide the username from a Credential without it being obfuscated. Have I misunderstood your comment? Many thanks.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this
[JIRA] (JENKINS-44860) Disable masking of usernames
Title: Message Title
Oliver Lockwood edited a comment on JENKINS-44860
Re: Disable masking of usernames
We came across this issue last week as well and, having discovered this issue, are contemplating contributing a fix.Just to be clear, we'd like to: * use the username/password credentials type * use the following pipeline script to provide username and password as environment variables to the pipeline script closure and e.g. any shell commands within it: {{withCredentials([usernamePassword(credentialsId: 'MY_CRED_ID', usernameVariable: 'USER_ENV_VAR', passwordVariable: 'PASSWORD_ENV_VAR')]) \{ ... }}} to provide username and password as environment variables to the pipeline script closure and e.g. any shell commands within it * have any instances of whatever the password is be masked in console output * NOT have any instances of whatever the username is masked in console output.This would then correlate correctly with the view on the {{jenkinsUrl/credentials}} page, which shows {{user-name/** (description)}} in the {{Name}} column for credentials of this type.[~jglick] we already found the {{UsernamePasswordMultiBinding}} class; but it looks to us (perhaps naively?) that the return value of the `bind()` method is used in {{BindingStep.Execution.start()}} *both* for actually providing the environment variables (through the use of {{EnvironmentExpander}}) *and* for obfuscating the secrets into {{}} (through the use of {{Filter}}). So it's not clear to me how the patch you're suggesting would allow us to still provide the username from a Credential without it being obfuscated. Have I misunderstood your comment? Many thanks.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49539) Jenkins cannot trigger load runner scenario
Title: Message Title Adrian David assigned an issue to Adrian David Jenkins / JENKINS-49539 Jenkins cannot trigger load runner scenario Change By: Adrian David Assignee: Yafim Kazak Adrian David Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49539) Jenkins cannot trigger load runner scenario
Title: Message Title Adrian David resolved as Fixed Jenkins / JENKINS-49539 Jenkins cannot trigger load runner scenario Change By: Adrian David Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50838) The plugin doesn't login anymore
Title: Message Title Thibaud Lepretre commented on JENKINS-50838 Re: The plugin doesn't login anymore You can check with https://my.gitlab.hosted.somewere.url.com/help Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title
Hugh Saunders commented on JENKINS-48061
Re: git plugin 3.6.4 regression with shared libraries
Hey Mark Waite, I built rsandell's branch at 887ac3394c48e844147de591277a0457adb345a3 but it didn't solve my problem. Version:
Git plugin
This plugin integrates Git with Jenkins.
3.8.1-SNAPSHOT (private-887ac339-hughsaunders)
Downgrade to 3.6.3
Console:
GitHub pull request #719 of commit f35de294eaebcbe5aecd824b444d1d901777814a, no merge conflicts.
Setting status of f35de294eaebcbe5aecd824b444d1d901777814a to PENDING with url https://rpc.jenkins.cit.rackspace.net/job/RPC-Pull-Request-Issue-Link_rpc_gating/1806/ and message: 'Build started sha1 is merged.'
Using context: CIT/issue-link
Running in Durability level: PERFORMANCE_OPTIMIZED
[Pipeline] library
Loading library rpc-gating@origin/pr/719/merge
Attempting to resolve origin/pr/719/merge from remote references...
> git --version # timeout=10
using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc
> git ls-remote -h https://github.com/rcbops/rpc-gating.git # timeout=10
Could not find origin/pr/719/merge in remote references. Pulling heads to local for deep search...
> git rev-parse --is-inside-work-tree # timeout=10
Setting origin to https://github.com/rcbops/rpc-gating.git
> git config remote.origin.url https://github.com/rcbops/rpc-gating.git # timeout=10
Fetching origin...
Fetching upstream changes from origin
> git --version # timeout=10
using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc
> git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/heads/origin/pr/*
> git rev-parse origin/pr/719/merge^{commit} # timeout=10
> git branch -a -v --no-abbrev --contains 10939c10d74f2284e1078a7371d49587d71858a1 # timeout=10
Could not find a branch containing commit 10939c10d74f2284e1078a7371d49587d71858a1
[Pipeline] End of Pipeline
[BFA] Scanning build for known causes...
[BFA] No failure causes found
[BFA] Done. 0s
Setting status of f35de294eaebcbe5aecd824b444d1d901777814a to FAILURE with url https://rpc.jenkins.cit.rackspace.net/job/RPC-Pull-Request-Issue-Link_rpc_gating/1806/ and message: 'Build finished. '
Using context: CIT/issue-link
ERROR: No version origin/pr/719/merge found for library rpc-gating
Finished: FAILURE
Its frustrating because the ref is obviously valid as
git rev-parse origin/pr/719/merge^{commit}
successfully translates it to a SHA.
[JIRA] (JENKINS-47427) Poll per change with pipeline jobs
Title: Message Title Paul Allen resolved as Fixed Ready for release. Jenkins / JENKINS-47427 Poll per change with pipeline jobs Change By: Paul Allen Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-44706) Tracking of P4 Credentials is slowing down REST API queries
Title: Message Title Paul Allen resolved as Fixed Ready for release. Jenkins / JENKINS-44706 Tracking of P4 Credentials is slowing down REST API queries Change By: Paul Allen Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-47999) Test scenario can't be started if deactivated sripts are included.
Title: Message Title Adrian David commented on JENKINS-47999 Re: Test scenario can't be started if deactivated sripts are included. Hi Sebastian, Can you update us if this thread is still relevant? Adrian Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-47999) Test scenario can't be started if deactivated sripts are included.
Title: Message Title Adrian David started work on JENKINS-47999 Change By: Adrian David Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48004) Test result analysis sometimes doesn't proceed after the test run is finished
Title: Message Title Adrian David started work on JENKINS-48004 Change By: Adrian David Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50838) The plugin doesn't login anymore
Title: Message Title Thibaud Lepretre commented on JENKINS-50838 Re: The plugin doesn't login anymore Ho OK thank for clarification so yes is 10.7 https://gitlab.com/help Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50939) Problem unmarshalling java.util.EnumSet
Title: Message Title Marcos Bento created an issue Jenkins / JENKINS-50939 Problem unmarshalling java.util.EnumSet Issue Type: Bug Assignee: Unassigned Components: prqa-plugin Created: 2018-04-23 10:08 Environment: PRQA Jenkins plugin 3.0.1 with Jenkins 2.107.2 Priority: Minor Reporter: Marcos Bento PRQA Jenkins plugin 3.0.1 reports the following issue while unmarshalling report information: ConversionException: Refusing to unmarshal chosenReportTypes for security reasons; see https://jenkins.io/redirect/class-filter/ Debugging information class : java.util.EnumSet required-type : java.util.EnumSet converter-type : hudson.util.XStream2$BlacklistedTypesConverter path : /build/actions/net.praqma.jenkins.plugin.prqa.notifier.PRQABuildAction/publisher/chosenReportTypes line number : 141 -- This problem seems to indicate the java.util.EnumSet is not being whitelisted in Jenkins. Add Comment
[JIRA] (JENKINS-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title
Hugh Saunders edited a comment on JENKINS-48061
Re: git plugin 3.6.4 regression with shared libraries
{color:#ff}*This failure was due to my config error, see my next comment.*{color} Hey [~markewaite], I built [~rsandell]'s branch at 887ac3394c48e844147de591277a0457adb345a3 but it didn't solve my problem. Version:{code:java}Git pluginThis plugin integrates Git with Jenkins.3.8.1-SNAPSHOT (private-887ac339-hughsaunders) Downgrade to 3.6.3{code}Console:{code:java}GitHub pull request #719 of commit f35de294eaebcbe5aecd824b444d1d901777814a, no merge conflicts.Setting status of f35de294eaebcbe5aecd824b444d1d901777814a to PENDING with url https://rpc.jenkins.cit.rackspace.net/job/RPC-Pull-Request-Issue-Link_rpc_gating/1806/ and message: 'Build started sha1 is merged.'Using context: CIT/issue-linkRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] libraryLoading library rpc-gating@origin/pr/719/mergeAttempting to resolve origin/pr/719/merge from remote references... > git --version # timeout=10using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc > git ls-remote -h https://github.com/rcbops/rpc-gating.git # timeout=10Could not find origin/pr/719/merge in remote references. Pulling heads to local for deep search... > git rev-parse --is-inside-work-tree # timeout=10Setting origin to https://github.com/rcbops/rpc-gating.git > git config remote.origin.url https://github.com/rcbops/rpc-gating.git # timeout=10Fetching origin...Fetching upstream changes from origin > git --version # timeout=10using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/heads/origin/pr/* > git rev-parse origin/pr/719/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains 10939c10d74f2284e1078a7371d49587d71858a1 # timeout=10Could not find a branch containing commit 10939c10d74f2284e1078a7371d49587d71858a1[Pipeline] End of Pipeline[BFA] Scanning build for known causes...[BFA] No failure causes found[BFA] Done. 0sSetting status of f35de294eaebcbe5aecd824b444d1d901777814a to FAILURE with url https://rpc.jenkins.cit.rackspace.net/job/RPC-Pull-Request-Issue-Link_rpc_gating/1806/ and message: 'Build finished. 'Using context: CIT/issue-linkERROR: No version origin/pr/719/merge found for library rpc-gatingFinished: FAILURE{code}Its frustrating because the ref is obviously valid as{code:java} git rev-parse origin/pr/719/merge^{commit}{code}successfully translates it to a SHA.As before, when running the commands manually, a branch is found:{code:java}10:08 $ git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/heads/origin/pr/*remote: Counting objects: 1319, done.remote: Compressing objects: 100% (12/12), done.remote: Total 1319 (delta 755), reused 753 (delta 752), pack-reused 555Receiving objects: 100% (1319/1319), 232.31 KiB | 1.40 MiB/s, done.Resolving deltas: 100% (830/830), completed with 453 local objects.From github.com:rcbops/rpc-gating* [new ref] refs/pull/1/head -> origin/pr/1/head* [new ref] refs/pull/10/head -> origin/pr/10/head* [new ref] refs/pull/100/head -> origin/pr/100/head...10:08 $ git branch -a -v --no-abbrev --contains 10939c10d74f2284e1078a7371d49587d71858a1origin/pr/719/merge 10939c10d74f2284e1078a7371d49587d71858a1 Merge f35de294eaebcbe5aecd824b444d1d901777814a into b0359387d639b5d7df8267f4fa09c0bba798a286{code}
[JIRA] (JENKINS-50940) Introduce a way to have build data only during Evergreen testing
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-50940 Introduce a way to have build data only during Evergreen testing Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50940) Introduce a way to have build data only during Evergreen testing
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-50940 Introduce a way to have build data only during Evergreen testing Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-04-23 10:36 Labels: essentials essentials-triggered Priority: Minor Reporter: Baptiste Mathus With JENKINS-50164, we are introducing system properties to better differentiate durable and less durable build data. To test this, we must run a job. This is a bit less than trivial with the current setup, so I'm filing this as a separate task to better clarify the intent and the task being worked on. I think it's time to introduce something like a test mode. A mode where where we will have data to help us test things that will be used in production, but that we obviously do not want to ship like a smoke testing job for instance. Add Comment
[JIRA] (JENKINS-50760) JEP-200 issue with plugin Kubernetes Continuous Deploy Plugin
Title: Message Title Oleg Nenashev updated JENKINS-50760 Fix has been released in kubernetes-cd-0.2.1 Jenkins / JENKINS-50760 JEP-200 issue with plugin Kubernetes Continuous Deploy Plugin Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50944) Increased code coverage for blueocean-pipeline-editor
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-50944 Increased code coverage for blueocean-pipeline-editor Issue Type: Improvement Assignee: Unassigned Components: blueocean-pipeline-editor-plugin Created: 2018-04-23 12:50 Priority: Minor Reporter: Karl Shultz Summary According to Jest lcov reports shown on ci.blueocean.io (example from latest, code coverage as reported by Jest is low. As of this writing: Statements: 5% Branches: 4% Functions: 4% Lines: 10% While it is generally understood that high code coverage numbers != test completeness, these numbers do seem low, especially when compared to other components in Blue Ocean. Add Comment
[JIRA] (JENKINS-50946) Increased code coverage for jenkins-design-language
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-50946 Increased code coverage for jenkins-design-language Issue Type: Improvement Assignee: Unassigned Components: blueocean-pipeline-editor-plugin Created: 2018-04-23 12:56 Priority: Minor Reporter: Karl Shultz Summary According to Jest lcov reports shown on ci.blueocean.io (example from latest, code coverage is low. As of this writing: Statements: 16% Branches: 13% Functions: 10% Lines: 19% While it is generally understood that high code coverage numbers != test completeness, these numbers do seem low, especially when compared to other components in Blue Ocean. Add Comment
[JIRA] (JENKINS-50920) NPM registry credentials not correctly formatted
Title: Message Title John Case commented on JENKINS-50920 Re: NPM registry credentials not correctly formatted e are not using Artifactory. We are using Verdaccio Publishing to it works manually with the authToken property as described in the issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50945) Increased code coverage for blueocean-web
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-50945 Increased code coverage for blueocean-web Issue Type: Improvement Assignee: Unassigned Components: blueocean-pipeline-editor-plugin Created: 2018-04-23 12:53 Priority: Minor Reporter: Karl Shultz Summary According to Jacoco reports shown on ci.blueocean.io (example from latest, code coverage is low. As of this writing: Instructions: 3% Branches: 6% While it is generally understood that high code coverage numbers != test completeness, these numbers do seem low, especially when compared to other components in Blue Ocean. Add Comment
[JIRA] (JENKINS-50920) NPM registry credentials not correctly formatted
Title: Message Title John Case edited a comment on JENKINS-50920 Re: NPM registry credentials not correctly formatted e We are not using Artifactory. We are using [Verdaccio|http://www.verdaccio.org/] Publishing to it works manually with the authToken property as described in the issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50767) Control initial crumb issuer proxy compatibility value
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50767 Re: Control initial crumb issuer proxy compatibility value Code changed in jenkins User: Vincent Latombe Path: core/src/main/java/jenkins/install/SetupWizard.java http://jenkins-ci.org/commit/jenkins/909f55b77da1d4a0a16a818fe592504538e49430 Log: JENKINS-50767 Control crumb issuer proxy compatibility through system property (#3389) -Djenkins.model.Jenkins.crumbIssuerProxyCompatibility=true enables proxy compatibility on startup Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48945) wrong testreport, if testnames produce a hashcollision (because of temp. generated junit-files)
Title: Message Title Sascha Friederich assigned an issue to Nikolas Falco Jenkins / JENKINS-48945 wrong testreport, if testnames produce a hashcollision (because of temp. generated junit-files) Change By: Sascha Friederich Assignee: Gregory Boissinot Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50767) Control initial crumb issuer proxy compatibility value
Title: Message Title Vincent Latombe updated JENKINS-50767 Jenkins / JENKINS-50767 Control initial crumb issuer proxy compatibility value Change By: Vincent Latombe Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48960) Org folders repository folder never runs scans on repository
Title: Message Title
Andy Airey edited a comment on JENKINS-48960
Re: Org folders repository folder never runs scans on repository
Tried [~tario] workaround againd again and got it working this time .Was trying [~jimklimov]'s one first but that didn't seem to find any jobs for me.Also, it requires the GroovyPostBuild plugin or it will not be able to use {{manager}}.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title
Hugh Saunders edited a comment on JENKINS-48061
Re: git plugin 3.6.4 regression with shared libraries
Update... I forgot to add the new trait, which explains the failure in my above comment. I retried, switching from github to git retrieval method and adding the new trait. I also removed the additional refspecs I had defined previously.Current config:!Screen Shot 2018-04-23 at 11.20.22.png!It now library checkout from a PR works again :D{code:java}GitHub pull request #719 of commit f35de294eaebcbe5aecd824b444d1d901777814a, no merge conflicts. Setting status of f35de294eaebcbe5aecd824b444d1d901777814a to PENDING with url https://rpc.jenkins.cit.rackspace.net/job/RPC-Pull-Request-Issue-Link_rpc_gating/1814/ and message: 'Build started sha1 is merged.' Using context: CIT/issue-link Running in Durability level: PERFORMANCE_OPTIMIZED [Pipeline] library Loading library rpc-gating@origin/pr/719/merge Attempting to resolve origin/pr/719/merge from remote references... > git --version # timeout=10 using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc > git ls-remote https://github.com/rcbops/rpc-gating.git # timeout=10 Could not find origin/pr/719/merge in remote references. Pulling heads to local for deep search... > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://github.com/rcbops/rpc-gating.git > git config remote.origin.url https://github.com/rcbops/rpc-gating.git # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* +refs/origin/pull/*/merge:refs/remotes/origin/origin/pull/*/merge > git rev-parse origin/pr/719/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains 10939c10d74f2284e1078a7371d49587d71858a1 # timeout=10 Selected match: pr/719/merge revision 10939c10d74f2284e1078a7371d49587d71858a1 > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/rcbops/rpc-gating.git # timeout=10 Fetching without tags Fetching upstream changes from https://github.com/rcbops/rpc-gating.git > git --version # timeout=10 using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc > git fetch --no-tags --progress https://github.com/rcbops/rpc-gating.git +refs/heads/*:refs/remotes/origin/* +refs/origin/pull/*/merge:refs/remotes/origin/origin/pull/*/merge JENKINS-19022: warning: possible memory leak due to Git plugin usage; see: https://wiki.jenkins-ci.org/display/JENKINS/Remove+Git+Plugin+BuildsByBranch+BuildData Checking out Revision 10939c10d74f2284e1078a7371d49587d71858a1 (pr/719/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f 10939c10d74f2284e1078a7371d49587d71858a1 Commit message: "Merge f35de294eaebcbe5aecd824b444d1d901777814a into b0359387d639b5d7df8267f4fa09c0bba798a286" > git rev-list --no-walk 1ab31cb8abfe1386c699bf6fbdb406f8105af82d # timeout=10 {code}
[JIRA] (JENKINS-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title
Hugh Saunders edited a comment on JENKINS-48061
Re: git plugin 3.6.4 regression with shared libraries
Update... I forgot to add the new trait, which explains the failure in my above comment. I retried, switching from github to git retrieval method and adding the new trait. I also removed the additional refspecs I had defined previously.Current config:!Screen Shot 2018-04-23 at 11.20.22.png! It now Now library checkout from a PR works again :D{code:java}GitHub pull request #719 of commit f35de294eaebcbe5aecd824b444d1d901777814a, no merge conflicts.Setting status of f35de294eaebcbe5aecd824b444d1d901777814a to PENDING with url https://rpc.jenkins.cit.rackspace.net/job/RPC-Pull-Request-Issue-Link_rpc_gating/1814/ and message: 'Build started sha1 is merged.'Using context: CIT/issue-linkRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] libraryLoading library rpc-gating@origin/pr/719/mergeAttempting to resolve origin/pr/719/merge from remote references... > git --version # timeout=10using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc > git ls-remote https://github.com/rcbops/rpc-gating.git # timeout=10Could not find origin/pr/719/merge in remote references. Pulling heads to local for deep search... > git rev-parse --is-inside-work-tree # timeout=10Setting origin to https://github.com/rcbops/rpc-gating.git > git config remote.origin.url https://github.com/rcbops/rpc-gating.git # timeout=10Fetching origin...Fetching upstream changes from origin > git --version # timeout=10using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* +refs/origin/pull/*/merge:refs/remotes/origin/origin/pull/*/merge > git rev-parse origin/pr/719/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains 10939c10d74f2284e1078a7371d49587d71858a1 # timeout=10Selected match: pr/719/merge revision 10939c10d74f2284e1078a7371d49587d71858a1 > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/rcbops/rpc-gating.git # timeout=10Fetching without tagsFetching upstream changes from https://github.com/rcbops/rpc-gating.git > git --version # timeout=10using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc > git fetch --no-tags --progress https://github.com/rcbops/rpc-gating.git +refs/heads/*:refs/remotes/origin/* +refs/origin/pull/*/merge:refs/remotes/origin/origin/pull/*/mergeJENKINS-19022: warning: possible memory leak due to Git plugin usage; see: https://wiki.jenkins-ci.org/display/JENKINS/Remove+Git+Plugin+BuildsByBranch+BuildDataChecking out Revision 10939c10d74f2284e1078a7371d49587d71858a1 (pr/719/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f 10939c10d74f2284e1078a7371d49587d71858a1Commit message: "Merge f35de294eaebcbe5aecd824b444d1d901777814a into b0359387d639b5d7df8267f4fa09c0bba798a286" > git rev-list --no-walk 1ab31cb8abfe1386c699bf6fbdb406f8105af82d # timeout=10{code}
[JIRA] (JENKINS-50419) PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2
Title: Message Title Marcos Bento updated JENKINS-50419 Jenkins / JENKINS-50419 PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2 Change By: Marcos Bento Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50419) PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2
Title: Message Title Marcos Bento updated JENKINS-50419 Jenkins / JENKINS-50419 PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2 Change By: Marcos Bento Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50419) PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2
Title: Message Title Marcos Bento started work on JENKINS-50419 Change By: Marcos Bento Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39179) All builds hang, JNA load deadlock on Windows slave
Title: Message Title pjdarton commented on JENKINS-39179 Re: All builds hang, JNA load deadlock on Windows slave Helder Magalhães You should be using Java 8 (aka 1.8) on both the master and slaves. Support for 1.7 ceased last year. See https://jenkins.io/blog/2017/04/10/jenkins-has-upgraded-to-java-8/ If you're using (very) different Javas on the masters and slaves then you can get weird errors. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50942) Increased code coverage for blueocean-jwt
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-50942 Increased code coverage for blueocean-jwt Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2018-04-23 12:44 Priority: Minor Reporter: Karl Shultz Summary According to Jacoco reports shown on ci.blueocean.io (example from latest, code coverage is lower than that of other Blue Ocean components. Instructions: 47% Branches: 20% While it is generally understood that high code coverage numbers != test completeness, these numbers do seem low, especially when compared to other components in Blue Ocean. Add Comment
[JIRA] (JENKINS-50943) Increased code coverage for blueocean-personalization
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-50943 Increased code coverage for blueocean-personalization Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2018-04-23 12:47 Priority: Minor Reporter: Karl Shultz Summary According to Jest lcov reports shown on ci.blueocean.io (example from latest, code coverage as reported by Jest is low. As of this writing: Statements: 34% Branches: 33% Functions: 24% Lines: 46% While it is generally understood that high code coverage numbers != test completeness, these numbers do seem low, especially when compared to other components in Blue Ocean. Add Comment
[JIRA] (JENKINS-50938) Wrong documentation for selectors
Title: Message Title Milan Hradil created an issue Jenkins / JENKINS-50938 Wrong documentation for selectors Issue Type: Bug Assignee: ikedam Components: copyartifact-plugin Created: 2018-04-23 10:00 Priority: Major Reporter: Milan Hradil There is a wrong value in the table of possible selectors. "lastCompletedLast" should be "lastCompleted" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48960) Org folders repository folder never runs scans on repository
Title: Message Title Andy Airey commented on JENKINS-48960 Re: Org folders repository folder never runs scans on repository Tried Patrick Ruckstuhl workaround againd and got it working. Was trying Jim Klimov's one first but that didn't seem to find any jobs for me. Also, it requires the GroovyPostBuild plugin or it will not be able to use manager. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Hugh Saunders updated an issue Jenkins / JENKINS-48061 git plugin 3.6.4 regression with shared libraries Change By: Hugh Saunders Attachment: Screen Shot 2018-04-23 at 11.20.22.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50419) PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2
Title: Message Title Marcos Bento commented on JENKINS-50419 Re: PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2 PRQA Jenkins 3.0.0+ only supports PRQA Framework 2.2.0+. As mentioned in the [documentation](https://wiki.jenkins.io/display/JENKINS/PRQA+Plugin), when using a previous version of the PRQA Framework please consider using an earlier version of the plugin from the [archive](https://updates.jenkins-ci.org/download/plugins/prqa-plugin/). For PRQA Framework 2.1.x, consider using PRQA Jenkins plugin 2.1.0. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50939) Problem unmarshalling java.util.EnumSet
Title: Message Title Marcos Bento started work on JENKINS-50939 Change By: Marcos Bento Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39179) All builds hang, JNA load deadlock on Windows slave
Title: Message Title Helder Magalhães updated an issue Jenkins / JENKINS-39179 All builds hang, JNA load deadlock on Windows slave Change By: Helder Magalhães Attachment: MyLinuxSlave-SystemInformation.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50939) Problem unmarshalling java.util.EnumSet
Title: Message Title Marcos Bento commented on JENKINS-50939 Re: Problem unmarshalling java.util.EnumSet PR 3403(https://github.com/jenkinsci/jenkins/pull/3403) submitted to fix this problem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39179) All builds hang, JNA load deadlock on Windows slave
Title: Message Title Helder Magalhães commented on JENKINS-39179 Re: All builds hang, JNA load deadlock on Windows slave @Jesse Glick: I've verified that the plug-in works properly for Windows slaves. Unfortunately we have a mixed installation base of Linux slaves as well, which break when "Launch slave agents via SSH" option is used: <===[JENKINS REMOTING CAPACITY]===>channel started Slave.jar version: 2.53.2 This is a Unix slave Preloading JNA to avoid JENKINS-39179 Slave JVM has not reported exit code. Is it still running? [04/23/18 08:29:08] Launch failed - cleaning up connection [04/23/18 08:29:08] [SSH] Connection closed. ERROR: Connection terminated I'm attaching MyLinuxSlave-SystemInformation.txt. May the problem be related with using a somehow old (1.7) Java version? Although it doesn't work (yet), thanks for the effort! I really prefer this to be the way (instead of changing configuration in all Windows nodes) until an official fix is provided. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50400) Build error for PRQA (build environment)
Title: Message Title Marcos Bento commented on JENKINS-50400 Re: Build error for PRQA (build environment) Priyanga G Can you provide me with more information about the issues you're facing? What error/symptom are you observing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title mike cirioli edited a comment on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found FYI, this look similar to [JENKINS-27548|https://issues.jenkins-ci.org/browse/JENKINS-27548] and [JENKINS-38895|https://issues.jenkins-ci.org/browse/JENKINS-38895] and [probably many of these as well|https://issues.jenkins-ci.org/browse/JENKINS-25456?jql=project%20%3D%20JENKINS%20AND%20text%20~%20%22Failed%20to%20persist%20config.xml%22]I haven't had a chance to read through them all and see if there is a solution for your problem, but will make some time this afternoon and see if there is anything to suggest. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title mike cirioli commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found FYI, this look similar to JENKINS-27548 and JENKINS-38895 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50850) createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0
Title: Message Title
Henti Smith commented on JENKINS-50850
Re: createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0
Chenyang Liu After running succesfully on 1.6.2, this morning the problem started again. I've since tested manually deploying a VM using our image on the azure portal, which failed with the same message
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"AllocationFailed\",\r\n \"message\": \"Allocation failed. Please try reducing the VM size or number of VMs, retry later, or try deploying to a different Availability Set or different Azure location.\"\r\n }\r\n ]\r\n }\r\n}"}]}
This seems to indicate that it is an Azure problem. While this ticket was created for the failure, I think it's important this ticket now highlight the lack of infrastructure failure/error handling. Clearly there are error states that indicate that either the Azure infrastructure is not available or that capacity in a specific region has been reached leading to deployment failures. Can this please be addressed in the short term with at least race mitigation so that the plugin does not attempt and fail at deploying 300+ VMs in an hour. For the long term, please add support for multi region handling of agents to mitigate localised regional failures in Azure.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50941) Increased code coverage for blueocean-dashboard
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-50941
Increased code coverage for blueocean-dashboard
Change By:
Karl Shultz
*Summary*According to Jest lcov reports shown on ci.blueocean.io (example from {{[latest|https://ci.blueocean.io/job/blueocean/job/master/lastSuccessfulBuild/artifact/blueocean-dashboard/target/jest-coverage/lcov-report/index.html]}}, code coverage as reported by Jest is low. As of this writing: * Statements: 10% * Branches: 9% * Functions: 7% * Lines: 17%While it is generally understood that high code coverage numbers != test completeness, these numbers do seem low, especially when compared to other components in Blue Ocean.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-50909) Using jenkins snapshots with the docker image makes some plugins to fail
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50909 Re: Using jenkins snapshots with the docker image makes some plugins to fail Code changed in jenkins User: Oleg Nenashev Path: Dockerfile README.md src/main/docker/installWARSnapshots.groovy src/main/docker/readJenkinsVersion.groovy src/main/docker/run-pct.sh http://jenkins-ci.org/commit/plugin-compat-tester/e015089812ad5462bcb8715ef85fabc1cfbe138a Log: JENKINS-50909 - Add support of running PCT for WAR and Plugin snapshots Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50909) Using jenkins snapshots with the docker image makes some plugins to fail
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50909 Re: Using jenkins snapshots with the docker image makes some plugins to fail Code changed in jenkins User: Oleg Nenashev Path: Dockerfile README.md src/main/docker/installWARSnapshots.groovy src/main/docker/readJenkinsVersion.groovy src/main/docker/run-pct.sh http://jenkins-ci.org/commit/plugin-compat-tester/f0d0ce72c68fe1ebd9952460235777b5eb434786 Log: Merge pull request #74 from oleg-nenashev/JENKINS-50909 JENKINS-50909 - Add support of running PCT for WAR and Plugin snapshots Compare: https://github.com/jenkinsci/plugin-compat-tester/compare/75c94910bf59...f0d0ce72c68f Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50920) NPM registry credentials not correctly formatted
Title: Message Title Nikolas Falco commented on JENKINS-50920 Re: NPM registry credentials not correctly formatted if you are using artifactory as company npm repository (as me), the email is required Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title
Hugh Saunders commented on JENKINS-48061
Re: git plugin 3.6.4 regression with shared libraries
Update... I forgot to add the new trait, which explains the failure in my above comment. I retried, switching from github to git retrieval method and adding the new trait. I also removed the additional refspecs I had defined previously. Current config: It now library checkout from a PR works again
GitHub pull request #719 of commit f35de294eaebcbe5aecd824b444d1d901777814a, no merge conflicts. Setting status of f35de294eaebcbe5aecd824b444d1d901777814a to PENDING with url https://rpc.jenkins.cit.rackspace.net/job/RPC-Pull-Request-Issue-Link_rpc_gating/1814/ and message: 'Build started sha1 is merged.' Using context: CIT/issue-link Running in Durability level: PERFORMANCE_OPTIMIZED [Pipeline] library Loading library rpc-gating@origin/pr/719/merge Attempting to resolve origin/pr/719/merge from remote references... > git --version # timeout=10 using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc > git ls-remote https://github.com/rcbops/rpc-gating.git # timeout=10 Could not find origin/pr/719/merge in remote references. Pulling heads to local for deep search... > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://github.com/rcbops/rpc-gating.git > git config remote.origin.url https://github.com/rcbops/rpc-gating.git # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* +refs/origin/pull/*/merge:refs/remotes/origin/origin/pull/*/merge > git rev-parse origin/pr/719/merge^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains 10939c10d74f2284e1078a7371d49587d71858a1 # timeout=10 Selected match: pr/719/merge revision 10939c10d74f2284e1078a7371d49587d71858a1 > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/rcbops/rpc-gating.git # timeout=10 Fetching without tags Fetching upstream changes from https://github.com/rcbops/rpc-gating.git > git --version # timeout=10 using GIT_ASKPASS to set credentials github_account_rpc_jenkins_svc > git fetch --no-tags --progress https://github.com/rcbops/rpc-gating.git +refs/heads/*:refs/remotes/origin/* +refs/origin/pull/*/merge:refs/remotes/origin/origin/pull/*/merge JENKINS-19022: warning: possible memory leak due to Git plugin usage; see: https://wiki.jenkins-ci.org/display/JENKINS/Remove+Git+Plugin+BuildsByBranch+BuildData Checking out Revision 10939c10d74f2284e1078a7371d49587d71858a1 (pr/719/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f 10939c10d74f2284e1078a7371d49587d71858a1 Commit message: "Merge f35de294eaebcbe5aecd824b444d1d901777814a into b0359387d639b5d7df8267f4fa09c0bba798a286" > git rev-list --no-walk 1ab31cb8abfe1386c699bf6fbdb406f8105af82d # timeout=10
[JIRA] (JENKINS-50939) Problem unmarshalling java.util.EnumSet
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50939 Problem unmarshalling java.util.EnumSet Change By: Oleg Nenashev Labels: JEP-200 core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50939) Problem unmarshalling java.util.EnumSet
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50939 Problem unmarshalling java.util.EnumSet Change By: Oleg Nenashev Labels: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50939) Problem unmarshalling java.util.EnumSet
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50939 Problem unmarshalling java.util.EnumSet Change By: Oleg Nenashev Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50910) Japex Plugin is not compatible with Jenkins 2.102+ due to serialization of weak references
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50910 Japex Plugin is not compatible with Jenkins 2.102+ due to serialization of weak references Change By: Oleg Nenashev Labels: JEP-200 JEP-200-rejected Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50910) Japex Plugin is not compatible with Jenkins 2.102+ due to serialization of weak references
Title: Message Title Oleg Nenashev commented on JENKINS-50910 Re: Japex Plugin is not compatible with Jenkins 2.102+ due to serialization of weak references Just to set an expectation, JEP-200 maintainers do not plan to fix this plugin. It has only 40 installations, and the code is outdated. The fix is trivial, but it just does not make sense unless there is somebody interested to maintain the plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50860) Multiple SSH connection using ssh key
Title: Message Title Daniel Beck closed an issue as Not A Defect This is an issue tracker, not a support site. Jenkins / JENKINS-50860 Multiple SSH connection using ssh key Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50941) Increased code coverage for blueocean-dashboard
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-50941 Increased code coverage for blueocean-dashboard Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2018-04-23 12:41 Priority: Minor Reporter: Karl Shultz Summary According to Jest lcov reports shown on ci.blueocean.io (example from latest, code coverage as reported by Jest is low. As of this writing: Statements: 10% Branches: 9% Functions: 7% Lines: 17% While it is generally understood that high code coverage numbers != test completeness, these numbers do seem low, especially when compared to other components in Blue Ocean. Add Comment
[JIRA] (JENKINS-50294) Design (JEP) Essentials Instance Client Health Checking
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50294 Re: Design (JEP) Essentials Instance Client Health Checking Code changed in jenkins User: Baptiste Mathus Path: jep//README.adoc http://jenkins-ci.org/commit/jep/958d5d2d7f8f1842e0bf8a06141e164010a7c11a Log: JENKINS-50294 Essentials Instance Client Health Checking Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title Oleg Nenashev commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ According to https://issues.jenkins-ci.org/browse/JENKINS-50899?focusedCommentId=335821=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-335821, my fix likely does not work as expected Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50616 JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Change By: Oleg Nenashev Labels: JEP-200 lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev commented on JENKINS-50616 Re: JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Created https://github.com/jenkinsci/jenkins/pull/3404. I do not believe it can be backported to 2.107.x, but CC Oliver Gondža just in case. It may need backporting to the next baseline anyway Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50616 JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Change By: Oleg Nenashev Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50737) An admin should be able to POST essentials.yaml and create a new Update record
Title: Message Title R. Tyler Croy started work on JENKINS-50737 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50849) Define the versions manifest schema
Title: Message Title R. Tyler Croy started work on JENKINS-50849 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Jesse Glick commented on JENKINS-50616 Re: JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Oleg Nenashev yes we should add RubyNil to the existing core whitelist—pending merge, release, and general adoption of the plugin fix. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev commented on JENKINS-50616 Re: JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons OK, will create a PR in few minutes Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50294) Design (JEP) Essentials Instance Client Health Checking
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50294 Re: Design (JEP) Essentials Instance Client Health Checking Code changed in jenkins User: R. Tyler Croy Path: jep/306/README.adoc jep/README.adoc http://jenkins-ci.org/commit/jep/d5c75cbae70a18055486f8550ec39cb9fa5cae4f Log: Merge pull request #91 from batmat/JENKINS-50294 JENKINS-50294 Essentials Instance Client Health Checking Compare: https://github.com/jenkinsci/jep/compare/b5d8196d8d9b...d5c75cbae70a Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50738) Instance versions information should be POSTable and history should be maintained
Title: Message Title R. Tyler Croy resolved as Fixed This has since been merged. Though the update levels are still giving me grief Jenkins / JENKINS-50738 Instance versions information should be POSTable and history should be maintained Change By: R. Tyler Croy Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-50947) Could not attach 'nodes/master/pipeline-timings.txt' to support bundle
Title: Message Title David Aldrich created an issue Jenkins / JENKINS-50947 Could not attach 'nodes/master/pipeline-timings.txt' to support bundle Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2018-04-23 15:08 Environment: Jenkins 2.107.2 Priority: Minor Reporter: David Aldrich With Support Core plugin 2.47 I see exceptions: Apr 23, 2018 2:19:06 PM WARNING com.cloudbees.jenkins.support.SupportPlugin writeBundle Could not attach 'nodes/master/pipeline-timings.txt' to support bundle java.io.IOException: Zodiac_build_gcc_vstudio_TRY_TML_VS2017_18Apr2018 #9 did not yet start at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:1058) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$PipelineTimings$1.writeTo(CpsFlowExecution.java:1779) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:357) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:271) at com.cloudbees.jenkins.support.SupportPlugin$PeriodicWorkImpl$1.run(SupportPlugin.java:741) at java.lang.Thread.run(Thread.java:748)
[JIRA] (JENKINS-50602) Add documentation on how to access credentials from within Jenkins pipelines
Title: Message Title James Nord closed an issue as Fixed Jenkins / JENKINS-50602 Add documentation on how to access credentials from within Jenkins pipelines Change By: James Nord Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49852) Collect Pipeline usage telemetry
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49852 Collect Pipeline usage telemetry Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49852) Collect Pipeline usage telemetry
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49852 Collect Pipeline usage telemetry Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48135) kubernetes-plugin should support multiple containers in declarative templates
Title: Message Title Carlos Sanchez updated JENKINS-48135 Jenkins / JENKINS-48135 kubernetes-plugin should support multiple containers in declarative templates Change By: Carlos Sanchez Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50949) Track update levels properly in the backend datastore
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50949 Track update levels properly in the backend datastore Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-04-23 16:03 Priority: Minor Reporter: R. Tyler Croy Per this discussion we need to keep track of update levels on the backend which requires a bit more machinery to get everything correct Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
