[JIRA] (JENKINS-33422) Provide a way to get back into Jenkins when active directory bind password expire
Title: Message Title Denys Digtiar commented on JENKINS-33422 Re: Provide a way to get back into Jenkins when active directory bind password expire According to https://plugins.jenkins.io/active-directory the fallback-user is available since 2.5. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168832.1457520387000.13419.1576736280317%40Atlassian.JIRA.
[JIRA] (JENKINS-50714) SonarQube Scanner 2.7 blocks Jenkins start
Title: Message Title Denys Digtiar resolved as Fixed Jenkins / JENKINS-50714 SonarQube Scanner 2.7 blocks Jenkins start Change By: Denys Digtiar Status: Open Resolved Resolution: Fixed Released As: 2.7.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189811.1523356411000.8309.1569895200587%40Atlassian.JIRA.
[JIRA] (JENKINS-52448) Requirements for Powershell DSL are unclear.
Title: Message Title Denys Digtiar resolved as Not A Defect There is a typo in the Pipeline. The step names are case sensitive. There is not powerShell step only powershell. Jenkins / JENKINS-52448 Requirements for Powershell DSL are unclear. Change By: Denys Digtiar Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192274.153121537.5260.1567485000215%40Atlassian.JIRA.
[JIRA] (JENKINS-52448) Requirements for Powershell DSL are unclear.
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-52448 Requirements for Powershell DSL are unclear. Change By: Denys Digtiar Component/s: durable-task-plugin Component/s: powershell-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192274.153121537.5258.1567484880133%40Atlassian.JIRA.
[JIRA] (JENKINS-53078) url encoded string doesn't work in powershell script
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-53078 url encoded string doesn't work in powershell script Change By: Denys Digtiar Labels: powershell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193072.1534450267000.5256.1567484760588%40Atlassian.JIRA.
[JIRA] (JENKINS-53078) url encoded string doesn't work in powershell script
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-53078 url encoded string doesn't work in powershell script Change By: Denys Digtiar Component/s: durable-task-plugin Component/s: powershell-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193072.1534450267000.5254.1567484760544%40Atlassian.JIRA.
[JIRA] (JENKINS-54618) Pipeline powershell step hangs if a function is called from powershell workflow
Title: Message Title Denys Digtiar commented on JENKINS-54618 Re: Pipeline powershell step hangs if a function is called from powershell workflow Changed the component to durable-task since that is where powershell step resides. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195351.1542013674000.5252.1567484640293%40Atlassian.JIRA.
[JIRA] (JENKINS-54618) Pipeline powershell step hangs if a function is called from powershell workflow
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-54618 Pipeline powershell step hangs if a function is called from powershell workflow Change By: Denys Digtiar Component/s: durable-task-plugin Component/s: powershell-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195351.1542013674000.5250.1567484640250%40Atlassian.JIRA.
[JIRA] (JENKINS-55585) Powershell plugin inside container hangs
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-55585 Powershell plugin inside container hangs Change By: Denys Digtiar Labels: powershell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196750.1547498858000.5247.1567484580293%40Atlassian.JIRA.
[JIRA] (JENKINS-55585) Powershell plugin inside container hangs
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-55585 Powershell plugin inside container hangs Change By: Denys Digtiar Component/s: durable-task-plugin Component/s: powershell-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196750.1547498858000.5245.1567484580270%40Atlassian.JIRA.
[JIRA] (JENKINS-55585) Powershell plugin inside container hangs
Title: Message Title Denys Digtiar commented on JENKINS-55585 Re: Powershell plugin inside container hangs Changing the component to durable-task since that is what implements the powershell step, not the PowerShell plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196750.1547498858000.5241.1567484520210%40Atlassian.JIRA.
[JIRA] (JENKINS-55596) PowerShell Plugin | Start-Job command creates TerminatingError(Import-Module)
Title: Message Title Denys Digtiar commented on JENKINS-55596 Re: PowerShell Plugin | Start-Job command creates TerminatingError(Import-Module) It sounds like the agent might be running on the 32-bit Java, therefore when it launches the PowerShell process it uses the 32-bit PowerShell. However, based on the error, the PowerShell-Workflow requires a 64-bit PowerShell. Hence, the solution is probably to install the 64-bit Java and make sure that the agent uses it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196762.1547549356000.5239.1567484460118%40Atlassian.JIRA.
[JIRA] (JENKINS-58165) support-core doesn't take into account %t on GC logs
Title: Message Title Denys Digtiar commented on JENKINS-58165 Re: support-core doesn't take into account %t on GC logs If you read closer the %p and %t are supported but the logic method is only called when the -XX:+UseGCLogFileRotation is present. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200216.1561384273000.2069.1562284020296%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58165) support-core doesn't take into account %t on GC logs
Title: Message Title
Denys Digtiar edited a comment on JENKINS-58165
Re: support-core doesn't take into account %t on GC logs
If you read closer the %p and %t are supported but the logic method is only called when the {{-XX:+UseGCLogFileRotation}} is present.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200216.1561384273000.2072.1562284020355%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57150) Need to connect to TFS online site through Jenkins
Title: Message Title Denys Digtiar assigned an issue to redsolo Jenkins / JENKINS-57150 Need to connect to TFS online site through Jenkins Change By: Denys Digtiar Assignee: Michael McCaskill redsolo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-57150) Need to connect to TFS online site through Jenkins
Title: Message Title Denys Digtiar moved an issue Jenkins / JENKINS-57150 Need to connect to TFS online site through Jenkins Change By: Denys Digtiar Project: Jenkins Website Key: WEBSITE JENKINS - 524 57150 Issue Type: Improvement Bug Workflow: WEBSITE: Software Development Workflow JNJira + In-Review Status: To Do Open Component/s: tfs-plugin Component/s: administrative Component/s: content Component/s: core Component/s: design Component/s: plugin-site
[JIRA] (JENKINS-43818) Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin
Title: Message Title Denys Digtiar assigned an issue to Mark Waite Jenkins / JENKINS-43818 Git fetch fails when "Branch Specifier" uses a parameter in new version of the Git plugin Change By: Denys Digtiar Assignee: Denys Digtiar Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56190) Master /proc files are added twice to the support bundle
Title: Message Title Denys Digtiar updated JENKINS-56190 Jenkins / JENKINS-56190 Master /proc files are added twice to the support bundle Change By: Denys Digtiar Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56190) Master /proc files are added twice to the support bundle
Title: Message Title Denys Digtiar started work on JENKINS-56190 Change By: Denys Digtiar Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56190) Master /proc files are added twice to the support bundle
Title: Message Title Denys Digtiar updated JENKINS-56190 Jenkins / JENKINS-56190 Master /proc files are added twice to the support bundle Change By: Denys Digtiar Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56190) Master /proc files are added twice to the support bundle
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-56190 Master /proc files are added twice to the support bundle Issue Type: Bug Assignee: Denys Digtiar Components: support-core-plugin Created: 2019-02-19 05:39 Priority: Minor Reporter: Denys Digtiar In linux, if you check to add Master system configuration (Linux only) and Agent system configuration (Linux only) as well, then the files from master are added twice to the bundle. Because the files from master are also gathered when using _Agent ... _ https://github.com/jenkinsci/support-core-plugin/blob/e2d79249818d4ea96979a710ac3404018f78/src/main/java/com/cloudbees/jenkins/support/impl/SystemConfiguration.java#L50-L66 Add Comment
[JIRA] (JENKINS-50160) Can't add credentials through https
Title: Message Title Denys Digtiar commented on JENKINS-50160 Re: Can't add credentials through https Anton Anonymous The X-Forwarded-Proto is the header your reverse proxy also needs to set, as far as I know. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52799) Powershell not able to get variables when using withCredentials
Title: Message Title Denys Digtiar commented on JENKINS-52799 Re: Powershell not able to get variables when using withCredentials Hi Tony Nguyen The environment variables should be exposed to powershell step the same as to bat or sh. Have you tried using $Env: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52799) Powershell not able to get variables when using withCredentials
Title: Message Title Denys Digtiar commented on JENKINS-52799 Re: Powershell not able to get variables when using withCredentials powershell step is provided by Pipeline: Nodes and Processes plugin. Updated the components accordingly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52799) Powershell not able to get variables when using withCredentials
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-52799 Powershell not able to get variables when using withCredentials Change By: Denys Digtiar Component/s: workflow-durable-task-step-plugin Component/s: powershell-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56076) Git Client plugin's CLI implementation does not interoperate with Kubernetes plugin
Title: Message Title
Denys Digtiar created an issue
Jenkins / JENKINS-56076
Git Client plugin's CLI implementation does not interoperate with Kubernetes plugin
Issue Type:
Improvement
Assignee:
Mark Waite
Attachments:
consoleText.txt
Components:
git-client-plugin, git-plugin
Created:
2019-02-11 06:24
Priority:
Minor
Reporter:
Denys Digtiar
When `checkout` or `git` steps run inside the Kubernetes plugin's `container` block the Git CLI is expected to be executed on the specified container but it is not. It is executed in the jnlp container disregarding the `container` step. Below is a test Pipeline. It relies on the custom docker image (duemir/jenkins-jnlp-agent:alpine-no-git) which is based on the `jenkins/jnlp-slave:alpine` Dockerfile but with `git` installation removed. The Console Output is attached. Env: Jenkins 2.138.4 Git plugin 3.9.1 Git Client plugin 2.7.3 Kuberentes plugin 1.12.8
pipeline {
agent {
kubernetes {
cloud 'kubernetes'
label 'custom-jnlp-without-git'
yaml """
kind: Pod
apiVersion: v1
spec:
containers:
- name: jnlp
image: duemir/jenkins-jnlp-agent:alpine-no-git
imagePullPolicy: Always
args: ['\$(JENKINS_SECRET)', '\$(JENKINS_NAME)']
- name: worker
image: jenkins/slave:latest
imagePullPolicy: Always
tty: true
command:
- /bin/sh
args:
- -c
- cat
"""
}
}
stages {
stage('Run') {
steps {
sh '''
echo This runs on jnlp container
git --version || true
'''
container('worker') {
sh '''
echo This runs on jnlp-slave container
[JIRA] (JENKINS-38084) Add support to mark jobs as disabled on import
Title: Message Title Denys Digtiar edited a comment on JENKINS-38084 Re: Add support to mark jobs as disabled on import The disable on import feature was lost when Folder import feature was merged. Please see [ https://github.com/jenkinsci/job-import-plugin/commit/594157a0404b25a87ace3f50c400559fa354e0c0 ] #diff-0034cbafb00263181c56677b9739d99aL130 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-38084) Add support to mark jobs as disabled on import
Title: Message Title Denys Digtiar reopened an issue The disable on import feature was lost when Folder import feature was merged. Please see https://github.com/jenkinsci/job-import-plugin/commit/594157a0404b25a87ace3f50c400559fa354e0c0 Jenkins / JENKINS-38084 Add support to mark jobs as disabled on import Change By: Denys Digtiar Resolution: Done Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title
Denys Digtiar commented on JENKINS-33510
Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Attila Szeremi So the defect indeed looks fixed and the issue appears to be with the file access now. Jenkins is trying to create a temp working directory besides the current working directory to write a shell script to but doesn't seem to have access to the `/var` directory. I would recommend reaching out to the mailing list or StackOverflow to get help with it if you have not yet solved it.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title
Denys Digtiar edited a comment on JENKINS-33510
Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
[~amcsi] If you Docker Pipeline plugin is 1.15 and Docker is 17.12 or newer then everything should just work no need to change the Pipeline . That is if I understand the fix correctly.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title
Denys Digtiar commented on JENKINS-33510
Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Attila Szeremi If you Docker Pipeline plugin is 1.15 and Docker is 17.12 or newer then everything should just work no need to change the Pipeline
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-54492) checkout scm information no longer injected into environment in pipeline job
Title: Message Title Denys Digtiar closed an issue as Not A Defect Jenkins / JENKINS-54492 checkout scm information no longer injected into environment in pipeline job Change By: Denys Digtiar Status: Reopened Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54492) checkout scm information no longer injected into environment in pipeline job
Title: Message Title Denys Digtiar updated JENKINS-54492 Jenkins / JENKINS-54492 checkout scm information no longer injected into environment in pipeline job Change By: Denys Digtiar Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54492) checkout scm information no longer injected into environment in pipeline job
Title: Message Title
Denys Digtiar updated JENKINS-54492
That is by design. The Pipeline can have multiple independent checkout steps which would override one another if they were all to expose to the same environment. Instead, the checkout steps returns an object that should contain all the environment variables that are exposed by SCM.
def svnInfo = checkout scm
echo "SVN_REVISION=${svnInfo.SVN_REVISION}"
Jenkins / JENKINS-54492
checkout scm information no longer injected into environment in pipeline job
Change By:
Denys Digtiar
Status:
Open Fixed but Unreleased
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-51985) Create official jenkins/jenkins Docker images for Java 10 and 11 versions
Title: Message Title Denys Digtiar assigned an issue to Unassigned Jenkins / JENKINS-51985 Create official jenkins/jenkins Docker images for Java 10 and 11 versions Change By: Denys Digtiar Assignee: Denys Digtiar Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50323) PullRequestSCMHead and PullRequestSCMRevision external use
Title: Message Title Denys Digtiar commented on JENKINS-50323 Re: PullRequestSCMHead and PullRequestSCMRevision external use Release notes say this was released in Version 2.4.0 https://plugins.jenkins.io/github-branch-source Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-53600) I would like to be able to remove Github.com from the API Endpoint option
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-53600 I would like to be able to remove Github.com from the API Endpoint option Issue Type: New Feature Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-09-17 03:48 Priority: Minor Reporter: Denys Digtiar As a Jenkins Admin, I would like to be able to limit the Repository scanning to self-hosted Github Enterprise server only Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-43693) multibranchPipelineJob overrides old branch indexing sources
Title: Message Title Denys Digtiar closed an issue as Fixed Jenkins / JENKINS-43693 multibranchPipelineJob overrides old branch indexing sources Change By: Denys Digtiar Status: Reopened 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-43693) multibranchPipelineJob overrides old branch indexing sources
Title: Message Title
Denys Digtiar edited a comment on JENKINS-43693
Re: multibranchPipelineJob overrides old branch indexing sources
Sorry, [~daspilker] . It looks like I misunderstood the resolution. Is the resolution to manually add unique Ids to the source definitions? Like this:{code:java}multibranchPipelineJob('job-dsl-plugin_multibranch') { branchSources {def repo = 'https://github.com/jenkinsci/job-dsl-plugin.git'git { id = UUID.nameUUIDFromBytes(repo.getBytes()) remote(repo)} }}{code}
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-43693) multibranchPipelineJob overrides old branch indexing sources
Title: Message Title Denys Digtiar commented on JENKINS-43693 Re: multibranchPipelineJob overrides old branch indexing sources Sorry, Daniel Spilker . It looks like I misunderstood the resolution. Is the resolution to manually add unique Ids to the source definitions? 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-43693) multibranchPipelineJob overrides old branch indexing sources
Title: Message Title Denys Digtiar reopened an issue I have created a fresh environment from 2.121 and installing: Pipeline: Multibranch 2.18 Github Branch Source Plugin 2.3.4 Job DSL 1.69 I was able to reproduce the issue using the steps in the description. I can still see Takeover for job-dsl-plugin_multibranch » master by source #1 from source that no longer exists Branch reopened: master (5045094d82daa475fe79e7f5e52eba58c6df9020) Scheduled build for branch: master after I re-run the Seed Job. Jenkins / JENKINS-43693 multibranchPipelineJob overrides old branch indexing sources Change By: Denys Digtiar Resolution: Fixed Status: Closed Reopened Add Comment
[JIRA] (JENKINS-38926) Add a report about the sandbox usage
Title: Message Title Denys Digtiar commented on JENKINS-38926 Re: Add a report about the sandbox usage Arnaud Héritier scriptAproval.xml is included in the bundle if the root configs component is selected. Do you think this is still relevant? 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-51256) properties step fails cryptically if previous build failed due to shard library loading error
Title: Message Title
Denys Digtiar created an issue
Jenkins / JENKINS-51256
properties step fails cryptically if previous build failed due to shard library loading error
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
stacktrace.txt, support_2018-05-11_00.32.02.zip
Components:
workflow-multibranch-plugin
Created:
2018-05-11 00:42
Environment:
macOS 10.13.4 jdk1.8.0_144 core 2.116 workflow-multibranch 2.18
Priority:
Minor
Reporter:
Denys Digtiar
For the sake of simplifying the reproduction steps, the simple Pipeline is used.
Create an empty git repo
Configure it as a implicitly loaded global shared library
Create a Pipeline:
properties([disableConcurrentBuilds()]) node { echo 'Hello World' }
Run the Pipeline and see it fail due to ERROR: Library library expected to contain at least one of src or vars directories
Add a sayHello step to the shared library https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-custom-steps
Run the Pipeline again
Actual: Build
[JIRA] (JENKINS-50337) BlueOcean does not show steps after a parallel step inside a script block
Title: Message Title Denys Digtiar commented on JENKINS-50337 Re: BlueOcean does not show steps after a parallel step inside a script block Hi Moritz Baumann. I believe this is a duplicate of the JENKINS-35836 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-46600) [JDK 9] Jenkins does not start with "java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter"
Title: Message Title Denys Digtiar commented on JENKINS-46600 Re: [JDK 9] Jenkins does not start with "java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter" As per http://openjdk.java.net/jeps/320 EE modules are going to be removed from the Java SE 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-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title Denys Digtiar commented on JENKINS-47834 Re: Add the support for Remoting work dir configuration of JNLP Launcher Oleg Nenashev no worries, completely understandable. I updated the description a bit. 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-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title
Denys Digtiar updated an issue
Jenkins / JENKINS-47834
Add the support for Remoting work dir configuration of JNLP Launcher
Change By:
Denys Digtiar
[https://jenkins.io/doc/upgrade-guide/2.73/] see Remoting Working Directories sectionSee screenshot for the new fields that were introduced to the JNLP Launcher.These appear to be ignored by the [Slave Setup|https://plugins.jenkins.io/slave-setup] and/or [Libvirt Slaves|https://plugins.jenkins.io/libvirt-slave] plugins which results result in the following two arguments are being added empty no matter what is in the fields{{-workDir}} {{}} {{-internalDir}} {{}}This seem seems to break the JNLP launcher since it apper appers to be defaultig to the `/` as path in such case.
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-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title
Denys Digtiar updated an issue
Jenkins / JENKINS-47834
Add the support for Remoting work dir configuration of JNLP Launcher
Change By:
Denys Digtiar
[https://jenkins.io/doc/upgrade-guide/2.73/] see Remoting Working Directories sectionSee screenshot for the new fields that were introduced to the JNLP Launcher.These appear to be ignored by the [Slave Setup|https://plugins.jenkins.io/slave-setup] and/or [Libvirt Slaves|https://plugins.jenkins.io/libvirt-slave] plugins which result in the following two arguments being added empty no matter what is in the fields{{-workDir}} {{}} {{-internalDir}} {{}}This seems to break the JNLP launcher since it appers appears to be defaultig defaulting to the `/` as a path in such case.
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-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title
Denys Digtiar updated an issue
Jenkins / JENKINS-47834
Add the support for Remoting work dir configuration of JNLP Launcher
Change By:
Denys Digtiar
[https://jenkins.io/doc/upgrade-guide/2.73/] see Remoting Working Directories sectionSee screenshot for the new fields that were introduced to the JNLP Launcher.These appear to be ignored by the [Slave Setup plugin |https://plugins.jenkins.io/slave-setup] and /or [Libvirt Slaves|https://plugins.jenkins.io/libvirt-slave] plugins which results the following two arguments are added no matter what is in the fields{{-workDir}} {{}} {{-internalDir}} {{}}This seem to break the JNLP launcher since it apper to be defaultig to the `/` as path in such case.
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-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title
Denys Digtiar updated an issue
Jenkins / JENKINS-47834
Add the support for Remoting work dir configuration of JNLP Launcher
Change By:
Denys Digtiar
[https://jenkins.io/doc/upgrade-guide/2.73/] see Remoting Working Directories sectionSee screenshot for the new fields that were introduced to the JNLP Launcher.These appear to be ignored by the [ Slave Setup plugin |https://plugins.jenkins.io/slave-setup] and the following two arguments are added no matter what is in the fields{{-workDir}}{{}}{{-internalDir}}{{}}This seem to break the JNLP launcher since it apper to be defaultig to the `/` as path in such case.
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-49668) Root CAs component appears broken
Title: Message Title Denys Digtiar resolved as Fixed Merged and ready for release. Jenkins / JENKINS-49668 Root CAs component appears broken Change By: Denys Digtiar 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-49668) Root CAs component appears broken
Title: Message Title Denys Digtiar updated JENKINS-49668 Jenkins / JENKINS-49668 Root CAs component appears broken Change By: Denys Digtiar Status: In Review 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-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title Denys Digtiar commented on JENKINS-47834 Re: Add the support for Remoting work dir configuration of JNLP Launcher Glenn Burkhardt I have only observed it in the Slave Setup Plugin. Therefore, I only placed in the slave-setup-plugin component which for some reason is being persistently removed. If you observe similar behavior with Libvirt Slaves plugin then it might be affected as well. 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-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-47834 Add the support for Remoting work dir configuration of JNLP Launcher Change By: Denys Digtiar Component/s: slave-setup-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-49668) Root CAs component appears broken
Title: Message Title Denys Digtiar updated JENKINS-49668 Jenkins / JENKINS-49668 Root CAs component appears broken Change By: Denys Digtiar 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-49668) Root CAs component appears broken
Title: Message Title Denys Digtiar started work on JENKINS-49668 Change By: Denys Digtiar 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-36997) sshAgent {} inside docker.image().inside {} does not work with long project name
Title: Message Title
Denys Digtiar edited a comment on JENKINS-36997
Re: sshAgent {} inside docker.image().inside {} does not work with long project name
[~hermain] As Mike and Jesse alluded to, the new Agent implementation was added which is based on the CLI {{ssh-agent}}. If you have a CLI available inside the docker container and use the `sshagent` inside the {{docker.inside()}} closure, your git clone should work. Looks Look for the message like "Exec ssh-agent (binary ssh-agent on a remote machine)" or any errors that mention {{ssh-agent}}
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-36997) sshAgent {} inside docker.image().inside {} does not work with long project name
Title: Message Title
Denys Digtiar commented on JENKINS-36997
Re: sshAgent {} inside docker.image().inside {} does not work with long project name
Hermann Schweizer As Mike and Jesse alluded to, the new Agent implementation was added which is based on the CLI ssh-agent. If you have a CLI available inside the docker container and use the `sshagent` inside the docker.inside() closure, your git clone should work. Looks for the message like "Exec ssh-agent (binary ssh-agent on a remote machine)" or any errors that mention ssh-agent
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-49668) Root CAs component appears broken
Title: Message Title Denys Digtiar assigned an issue to Denys Digtiar Jenkins / JENKINS-49668 Root CAs component appears broken Change By: Denys Digtiar Assignee: Denys Digtiar 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-49668) Root CAs component appears broken
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-49668 Root CAs component appears broken Issue Type: Bug Assignee: Unassigned Components: support-core-plugin Created: 2018-02-21 07:35 Environment: core 2.89.4 support-core 2.44 Java 1.8.0_121 Priority: Minor Reporter: Denys Digtiar It looks the component just tries to list an uninitialized KeyStore which results in: java.security.KeyStoreException: Uninitialized keystore at java.security.KeyStore.aliases(KeyStore.java:1233) at com.cloudbees.jenkins.support.impl.RootCAs.getRootCAList(RootCAs.java:149) at com.cloudbees.jenkins.support.impl.RootCAs$GetRootCA.call(RootCAs.java:132) at com.cloudbees.jenkins.support.impl.RootCAs$GetRootCA.call(RootCAs.java:125) at hudson.remoting.LocalChannel$1.call(LocalChannel.java:52) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) For reference on how to do it: https://stackoverflow.com/questions/8884831/listing-certificates-in-jvm-trust-store https://github.com/jenkinsci/jenkins-scripts/pull/82/files
[JIRA] (JENKINS-45575) Multiple assignment in pipeline fails with LHS Error
Title: Message Title Denys Digtiar commented on JENKINS-45575 Re: Multiple assignment in pipeline fails with LHS Error Andrew Bayer It sound's like I don't need to raise a separate script-security ticket after all. Correct? 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-39482) GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline
Title: Message Title Denys Digtiar commented on JENKINS-39482 Re: GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline FYI, I raised JENKINS-43182 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-43182) API to get SCMs of the current Pipeline build
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-43182 API to get SCMs of the current Pipeline build Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2017/Mar/29 7:52 AM Priority: Minor Reporter: Denys Digtiar Need for there to be at least one successful build for SCMs to show up in the current API, can cause a degradation in some of the features. The example that I am aware of is JENKINS-39482 Would it be possible to provide an API to enable access to the SCMs currently known to the executing Pipeline build, or some alternative? One defect is not an overwhelming evidence of a need for such API, but I wanted to get the idea out there. Add Comment
[JIRA] (JENKINS-42185) Add support for the Pipeline Projects
Title: Message Title Denys Digtiar commented on JENKINS-42185 Re: Add support for the Pipeline Projects Michal Slusarczyk FYI. I raised an Improvement ticket for you PR. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42185) Add support for the Pipeline Projects
Title: Message Title Denys Digtiar commented on JENKINS-42185 Re: Add support for the Pipeline Projects Some work has already been done in PR#21. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42185) Add support for the Pipeline Projects
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-42185 Add support for the Pipeline Projects Issue Type: Improvement Assignee: Mikael Gaunin Components: configurationslicing-plugin Created: 2017/Feb/20 7:03 AM Priority: Minor Reporter: Denys Digtiar Pipeline Project should be supported where possible. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40368) Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource
Title: Message Title Denys Digtiar commented on JENKINS-40368 Re: Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource recampbell Not sure exactly what stack trace to supply. Bellow is the FlowInterruptedException stack trace from when I click on forcible termination link. ERROR: Execution failed org.jenkinsci.plugins.workflow.steps.FlowInterruptedException at org.jenkinsci.plugins.workflow.job.WorkflowRun.doTerm(WorkflowRun.java:323) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:108) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:80) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] (JENKINS-41097) Time spent in {{artifactory.upload}} step is counted towards the previous step
Title: Message Title
Denys Digtiar updated an issue
Jenkins / JENKINS-41097
Time spent in {{artifactory.upload}} step is counted towards the previous step
Change By:
Denys Digtiar
Bellow is the Pipeline for reproducing the issue. All the time the upload is happening the logs show the {{fileExists}} step and when completed all the time is recorded towards the {{fileExists}}, which is the step right before the Artifactory upload.{code}node {deleteDir()def server = Artifactory.server "localhost-artifactory"stage('Build') {sh 'dd if=/dev/zero of=artifact.dat bs=1M count=1000'}stage('Release') {fileExists "artifact.dat"// Behold! Artifactory Uploadserver.upload """{"files": [{"pattern": "artifact.dat","target": " dump simple-repo / cloudbees/ZD my - 43888 artifact /artifact-${env.BUILD_NUMBER}.dat"}]}"""}}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41097) Time spent in {{artifactory.upload}} step is counted towards the previous step
Title: Message Title
Denys Digtiar edited a comment on JENKINS-41097
Re: Time spent in {{artifactory.upload}} step is counted towards the previous step
[ HAP-870 |https://www.jfrog.com/jira/browse/HAP-870] in JFrog JIRA might be a symptom of the same issue.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41097) Time spent in {{artifactory.upload}} step is counted towards the previous step
Title: Message Title
Denys Digtiar commented on JENKINS-41097
Re: Time spent in {{artifactory.upload}} step is counted towards the previous step
HAP-870 in JFrog JIRA might be a symptom of the same issue.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41097) Time spent in {{artifactory.upload}} step is counted towards the previous step
Title: Message Title
Denys Digtiar created an issue
Jenkins / JENKINS-41097
Time spent in {{artifactory.upload}} step is counted towards the previous step
Issue Type:
Bug
Assignee:
Eyal Ben Moshe
Attachments:
artifactory-upload-step-is-not-timestamped-correctly.png
Components:
artifactory-plugin
Created:
2017/Jan/16 6:13 AM
Environment:
Core 2.40 (jenkinsci/jenkins docker image) Artifactory 2.8.2
Priority:
Minor
Reporter:
Denys Digtiar
Bellow is the Pipeline for reproducing the issue. All the time the upload is happening the logs show the fileExists step and when completed all the time is recorded towards the fileExists, which is the step right before the Artifactory upload.
node {
deleteDir()
def server = Artifactory.server "localhost-artifactory"
stage('Build') {
sh 'dd if=/dev/zero of=artifact.dat bs=1M count=1000'
}
stage('Release') {
fileExists "artifact.dat"
// Behold! Artifactory Upload
server.upload """{
"files": [
{
"pattern": "artifact.dat",
"target": "dump/cloudbees/ZD-43888/artifact-${env.BUILD_NUMBER}.dat"
}
]
}"""
}
}
[JIRA] (JENKINS-41091) git-parameter:0.7.1 breaks the multi-line parameters in rebuild
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-41091 git-parameter:0.7.1 breaks the multi-line parameters in rebuild Issue Type: Bug Assignee: Boguslaw Klimas Attachments: rebuild_git_parameters_0_7_1_installed.png, rebuild_no_git-parameter.png Components: git-parameter-plugin Created: 2017/Jan/15 11:04 PM Environment: Docker: jenkinsci/jenkins:2.40 Priority: Minor Reporter: Denys Digtiar Installing Git Parameter Plugin version 0.7.1 makes multi-line parameters appear as a single line in the Rebuild page, see attached screenshots. Add Comment
[JIRA] (JENKINS-40701) Add warning that Usage Tracking might not be exhaustive and depends on the consumer plugins
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-40701 Add warning that Usage Tracking might not be exhaustive and depends on the consumer plugins Issue Type: Bug Assignee: Stephen Connolly Components: credentials-plugin Created: 2016/Dec/28 4:41 AM Priority: Minor Reporter: Denys Digtiar Until all the Credential consumers support the Usage Tracking API this feature might give a false impression that Credential is not used and can be deleted while it is still in use by the plugin which simply does not report the usage. Generic disclaimer or a way to detect and report the plugins which are not reporting usage should failproof this feature a bit. Add Comment
[JIRA] (JENKINS-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Denys Digtiar commented on JENKINS-38228 Re: Incorrect implementation of `loadUserByUsename`, Users are added on demand Ivan Fernandez Calvo are we talking about the same thing? This is not about Id that IdP returns. Changing UserName will not make any difference. The problem is that SamlUserDetailsService to reconstruct User uses API that creates Users on demand. No matter what username Authorization Strategy query from SamlSecurityRealm it says such user exists because it creates them on demand. The fix in PR is just changing the `User#get` method to the one that is not creating users by default. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Denys Digtiar commented on JENKINS-38228 Re: Incorrect implementation of `loadUserByUsename`, Users are added on demand It is still an issue I believe. Linking a fix which should make it more clear. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Denys Digtiar reopened an issue Jenkins / JENKINS-38228 Incorrect implementation of `loadUserByUsename`, Users are added on demand Change By: Denys Digtiar Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40368) Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource
Title: Message Title
Denys Digtiar created an issue
Jenkins / JENKINS-40368
Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource
Issue Type:
Bug
Assignee:
Unassigned
Components:
lockable-resources-plugin
Created:
2016/Dec/12 1:11 AM
Environment:
lockable-resources:1.10
Labels:
pipeline robustness
Priority:
Major
Reporter:
Denys Digtiar
Resource lock is not always released when there is some contention over it. This can, intermittently, be reproduced by running two builds of the below pipeline concurrently. Retry will simulate inability to cancel the build which should make hard kill link to appear. Canceling the builds in turn as they acquire the lock will sometimes produce the dangling lock.
retry(5) {
node('linux') {
lock('my-resource') {
println ("running find")
sh "find / -name hello.txt"
}
}
}
[JIRA] (JENKINS-23309) Upstream changes are not displayed for Folder contained jobs
Title: Message Title Denys Digtiar commented on JENKINS-23309 Re: Upstream changes are not displayed for Folder contained jobs Rob Petti thank you very much! 0.3.2 is in the update center and works nicely. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39015) Support hudson.model.UnprotectedRootAction
Title: Message Title Denys Digtiar commented on JENKINS-39015 Re: Support hudson.model.UnprotectedRootAction Thank you Oliver Gondža! The workaround worked for me. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38175) Preparing Jenkins for shutdown via Manage Jenkins -> system-log-out.png throws an HTTP 405 (POST is required for jenkins.model.Jenkins.doQuietDown); works fine via "Prepare for
Title: Message Title Denys Digtiar commented on JENKINS-38175 Re: Preparing Jenkins for shutdown via Manage Jenkins -> system-log-out.png throws an HTTP 405 (POST is required for jenkins.model.Jenkins.doQuietDown); works fine via "Prepare for Shutdown" link Can also be reproduced from a drop-down menu in the breadcrumbs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38175) Preparing Jenkins for shutdown via Manage Jenkins -> system-log-out.png throws an HTTP 405 (POST is required for jenkins.model.Jenkins.doQuietDown); works fine via "Prepare for
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-38175 Preparing Jenkins for shutdown via Manage Jenkins -> system-log-out.png throws an HTTP 405 (POST is required for jenkins.model.Jenkins.doQuietDown); works fine via "Prepare for Shutdown" link Change By: Denys Digtiar Attachment: jenkins_2_19_1_dropdown_menu.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23309) Upstream changes are not displayed for Folder contained jobs
Title: Message Title Denys Digtiar reopened an issue The latest version available in Update Center is 0.1. Could this fix be released to the greater public, please? Jenkins / JENKINS-23309 Upstream changes are not displayed for Folder contained jobs Change By: Denys Digtiar Resolution: Fixed Status: Closed Reopened Assignee: Rob Petti Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39015) Support hudson.model.UnprotectedRootAction
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-39015 Support hudson.model.UnprotectedRootAction Issue Type: New Feature Assignee: Tomas Westling Components: kerberos-sso-plugin Created: 2016/Oct/17 1:41 AM Priority: Minor Reporter: Denys Digtiar For better compatibility with standard behavior skip the authentication of URLs reported by the UnprotectedRootAction. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title Denys Digtiar commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents My test case is passing. Parameters are stored on SSH agent as well as the master. Thank you! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title Denys Digtiar commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents If the priority is from the perspective of overall Jenkins, then you are absolutely correct. I downgraded the priority. It was just my misunderstanding. Thank you for your prompt response, very much appreciated. I will test the fix and provide a feedback. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-38917 Version 1.8 stopped working with remote agents Change By: Denys Digtiar Priority: Blocker Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title Denys Digtiar edited a comment on JENKINS-38917 Re: Version 1.8 stopped working with remote agents I have not found it in archives so I built it from source. I was able to reproduce it the issue . I can not reproduce it the issue on 1.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title Denys Digtiar commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents I have not found it in archives so I built it from source. I was able to reproduce it. I can not reproduce it on 1.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title Denys Digtiar commented on JENKINS-38917 Re: Version 1.8 stopped working with remote agents I have just been able to reproduce it again with the brand new jenkins:alpine image based container and the same ssh agent container I used with the previous experiment. As I described it, the only workaround for the issue is to build on the master which is not feasible in the production environments, therefore Blocker priority. Here is a link to the change log for the last release pointing to the change that I believe is a culprit. https://github.com/jenkinsci/export-params-plugin/compare/export-params-1.1...export-params-1.8#diff-760dab5c086e6b7560887018ac881ac7L137 I don't know that much about Jenkins remoting. But my guess is that FileCallable has to be Serializable. Since an anonymous inner class is used it captures its parent object which I am guessing is not serializable or has fields in its hierarchy that are not serializable. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38917) Version 1.8 stopped working with remote agents
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-38917 Version 1.8 stopped working with remote agents Issue Type: Bug Assignee: rin_ne Components: export-params-plugin Created: 2016/Oct/12 7:08 AM Environment: Jenkins 1.625 LTS (on mac os sierra) export-params-plugin 1.8 docker jenkinsci/ssh-slave as an agent Labels: plugin remoting Priority: Blocker Reporter: Denys Digtiar While it works on the master when a Job is executed on a remote Agent the "export parameters to file" build step consistently fails with the following message. Could not store parameters into Further investigation uncovered following Exception as a cause java.io.IOException: remote file operation failed: at hudson.remoting.Channel@7f287e48:SSH1: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@38a67991 at hudson.FilePath.act(FilePath.java:987) at hudson.FilePath.act(FilePath.java:969) at org.jenkinsci.plugins.exportparams.ExportParametersBuilder.perform(ExportParametersBuilder.java:134) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at
[JIRA] (JENKINS-33193) UnsatisfiedLinkError after a Windows agent's service fails to restart
Title: Message Title Denys Digtiar commented on JENKINS-33193 Re: UnsatisfiedLinkError after a Windows agent's service fails to restart Looks like it may happen on master as well when SCM polling is done. 2016-09-21 04:51:02.118-0400 [id=57626] SEVERE h.triggers.SCMTrigger$Runner#runPolling: Failed to record SCM polling for hudson.maven.MavenModuleSet@5b64cc8d[...]java.lang.UnsatisfiedLinkError: com.microsoft.tfs.jni.internal.platformmisc.NativePlatformMisc.nativeGetEnvironmentVariable(Ljava/lang/String;)Ljava/lang/String; at com.microsoft.tfs.jni.internal.platformmisc.NativePlatformMisc.nativeGetEnvironmentVariable(Native Method) at com.microsoft.tfs.jni.internal.platformmisc.NativePlatformMisc.getEnvironmentVariable(NativePlatformMisc.java:134) at com.microsoft.tfs.jni.PlatformMiscUtils.getEnvironmentVariable(PlatformMiscUtils.java:52) at com.microsoft.tfs.core.config.EnvironmentVariables.getString(EnvironmentVariables.java:251) at com.microsoft.tfs.core.config.EnvironmentVariables.getBoolean(EnvironmentVariables.java:235) at com.microsoft.tfs.core.config.httpclient.DefaultHTTPClientFactory.getUserAgent(DefaultHTTPClientFactory.java:365) at com.microsoft.tfs.core.config.httpclient.DefaultHTTPClientFactory.configureClientParams(DefaultHTTPClientFactory.java:323) at com.microsoft.tfs.core.config.httpclient.DefaultHTTPClientFactory.newHTTPClient(DefaultHTTPClientFactory.java:142) at com.microsoft.tfs.core.TFSConnection.getHTTPClient(TFSConnection.java:1066) at com.microsoft.tfs.core.TFSConnection.getWebService(TFSConnection.java:860) at com.microsoft.tfs.core.clients.registration.RegistrationClient.(RegistrationClient.java:123) at com.microsoft.tfs.core.clients.registration.RegistrationClient.(RegistrationClient.java:97) at com.microsoft.tfs.core.config.client.DefaultClientFactory$4.newClient(DefaultClientFactory.java:192) at com.microsoft.tfs.core.config.client.DefaultClientFactory.newClient(DefaultClientFactory.java:98) at com.microsoft.tfs.core.TFSConnection.getClient(TFSConnection.java:1508) at com.microsoft.tfs.core.TFSTeamProjectCollection.getRegistrationClient(TFSTeamProjectCollection.java:366) at com.microsoft.tfs.core.clients.webservices.IdentityManagementService.(IdentityManagementService.java:64) at hudson.plugins.tfs.model.Server.createIdentityManagementService(Server.java:213) at hudson.plugins.tfs.model.Project.getOrCreateUserLookup(Project.java:112) at hudson.plugins.tfs.model.Project.getVCCHistory(Project.java:82) at hudson.plugins.tfs.model.Project.getLatestUncloakedChangeset(Project.java:179) at hudson.plugins.tfs.TeamFoundationServerScm.compareRemoteRevisionWith(TeamFoundationServerScm.java:574) at hudson.scm.SCM.poll(SCM.java:398) at hudson.model.AbstractProject._poll(AbstractProject.java:1453) at hudson.model.AbstractProject.poll(AbstractProject.java:1356) at jenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:526) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:555) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
[JIRA] (JENKINS-36318) No Configuration UI
Title: Message Title Denys Digtiar commented on JENKINS-36318 Re: No Configuration UI Did you check the "Global Tool Configuration"? I believe it has moved there. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38034) SAML Plugin does not load groups when access with API Token
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-38034 SAML Plugin does not load groups when access with API Token Change By: Denys Digtiar Labels: SAML2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Denys Digtiar updated an issue Jenkins / JENKINS-38228 Incorrect implementation of `loadUserByUsename`, Users are added on demand Change By: Denys Digtiar Labels: SAML2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Denys Digtiar assigned an issue to Unassigned Jenkins / JENKINS-37289 authentication issue instant is too old or in the future Change By: Denys Digtiar Assignee: Ben McCann Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-38228 Incorrect implementation of `loadUserByUsename`, Users are added on demand Issue Type: Bug Assignee: Unassigned Components: saml-plugin Created: 2016/Sep/15 7:27 AM Environment: Jenkins Docker 2.7.4-alpine saml-plugin 0.6 Priority: Major Reporter: Denys Digtiar Steps to reproduce: 1. Setup the SAML Security Realm 2. Switch to any of the Matrix Authorization strategies 3. Add a random string of characters as users Expected Users mark with appropriate icon as non-existent (i.e. crossed out, icon with a cross) Actual User are added to the Jenkins, see People to confirm. Add Comment
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Denys Digtiar commented on JENKINS-37289 Re: authentication issue instant is too old or in the future Coltrey Mather I can't answer the question about the release. I just added a link to make sure that maintainer is aware of the relation. The issue was in the order of the calls. Saml2Client initialization is costly, so it is triggered once lazily in certain methods. client.printClientMetadata() is one of those methods. Since it was called before setMaximumAuthenticationLifetime(), the new value of the Maximum Authentication Lifetime was disregarded in future calls to the client. The fix changes the order of the method calls to allow for the proper initialization of the client. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Denys Digtiar commented on JENKINS-37289 Re: authentication issue instant is too old or in the future Appears to be fixed on master. See the link. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33526) Support generation of the SAML metadata that can be consumed by IdPs
Title: Message Title Denys Digtiar commented on JENKINS-33526 Re: Support generation of the SAML metadata that can be consumed by IdPs Implemented in saml-0.6. The URL is http://JENKINS_HOST/securityRealm/metadata Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29086) User IDs are case sensitive in saml-plugin
Title: Message Title Denys Digtiar commented on JENKINS-29086 Re: User IDs are case sensitive in saml-plugin Looks like this has been released in saml-0.5 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
