[JIRA] [mercurial-plugin] (JENKINS-30871) Workflows are executed multiple times if they take longer than their poll period
Title: Message Title Gregory Symons created an issue Jenkins / JENKINS-30871 Workflows are executed multiple times if they take longer than their poll period Issue Type: Bug Assignee: Jesse Glick Components: mercurial-plugin, workflow-plugin Created: 10/Oct/15 12:40 AM Environment: Jenkins version: 1.609.1 Workflow Plugin version: 1.10 Mercurial Plugin version: 1.54 Labels: scm workflow Priority: Minor Reporter: Gregory Symons When executing a workflow build that is triggered by SCM polling, if a triggered run takes longer than the polling period to complete, then additional runs will be scheduled every time the polling period expires until the initially triggered build completes. I've only seen this issue with the mercurial plugin so far, but I don't really have any builds that use any other SCM plugins, so that doesn't necessarily mean anything. A minimal workflow that should recreate the problem is below (fill in your own SCM details):
[JIRA] [analysis-core-plugin] (JENKINS-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Gregory Symons created an issue Jenkins / JENKINS-31202 Trend Graphs are not shown in Job view for Workflow builds Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core-plugin Created: 27/Oct/15 9:58 PM Environment: Jenkins Version: 1.609.1 analysis-core version: 1.74 Priority: Minor Reporter: Gregory Symons The Job-level trend graphs for the static analyses I run (checkstyle, warnings, and tasks) are not showing up. The reports are being generated and published correctly at the run level, but I don't have any trending. Is there a configuration option I may have missed? Add Comment
[JIRA] [docker-workflow-plugin] (JENKINS-28821) Docker Workflow demos: sh step on Docker image hangs if workspace is not writable
Title: Message Title Gregory Symons commented on JENKINS-28821 Re: Docker Workflow demos: sh step on Docker image hangs if workspace is not writable In my case, I was running Jenkins in a container, and had mounted the host's Docker socket in the container. Since /var/jenkins_home was a data volume for the container, it didn't exist on the host, and so the workspace didn't exist either. I fixed it by running a second Docker process inside the container alongside Jenkins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-28821) Docker Workflow demos: sh step on Docker image hangs if workspace is not writable
Title: Message Title
Greg Symons commented on JENKINS-28821
Re: Docker Workflow demos: sh step on Docker image hangs if workspace is not writable
This problem occurs even when using a local docker via socket. See the example below:
docker.image('java:openjdk-7-jre').inside {
sh 'java -version'
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-29045) Mercurial plugin does not work inside container with Docker Workflow plugin
Title: Message Title
Greg Symons created an issue
Jenkins / JENKINS-29045
Mercurial plugin does not work inside container with Docker Workflow plugin
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
docker-workflow-plugin
Created:
23/Jun/15 8:41 PM
Environment:
Jenkins 1.609.1 Plugins: workflow 1.8 mercurial 1.54 docker-workflow 1.0 docker 1.6.2 jenkins itself is running in a docker container; access to docker daemon is through shared host unix socket
Labels:
plugin workflow
Priority:
Blocker
Reporter:
Greg Symons
The build fails with an AbortException when attempting to do a mercurial checkout inside a container when using the Docker workflow plugin:
Workflow:
stage 'Build'
node {
docker.image('gregsymons/sbt-build').inside {
checkout([$class: 'MercurialSCM',
credentialsId: '69d57484-a048-4ab2-88b1-7483b800bd20',
[JIRA] [docker-workflow-plugin] (JENKINS-29046) NPE when using withDockerRegistry
Title: Message Title
Greg Symons created an issue
Jenkins / JENKINS-29046
NPE when using withDockerRegistry
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
docker-workflow-plugin
Created:
23/Jun/15 9:01 PM
Environment:
Jenkins 1.609.1 Plugins: workflow 1.8 docker-workflow 1.0 docker 1.6.2 jenkins itself is running in a docker container; access to docker daemon is through shared host unix socket
Priority:
Blocker
Reporter:
Greg Symons
I get a NullPointerException when I try to use the withDockerRegistry step from the docker workflow plugin.
Workflow:
stage 'Build'
node {
withDockerRegistry(url: 'https://docker-registry.example.com', credentialsId: '69d57484-a048-4ab2-88b1-7483b800bd20') {
docker.image('docker-registry.example.com/infrastructure/sbt-build').inside {
checkout([$class: 'MercurialSCM',
credentialsId: '69d57484-a048-4ab2-88b1-7483b800bd20',
source: 'https://hg.example.com/my/repo'])
}
}
}
Output:
[JIRA] [docker-workflow-plugin] (JENKINS-29045) Mercurial plugin does not work inside container with Docker Workflow plugin
Title: Message Title Greg Symons resolved as Fixed This seems to have been a side-effect of the way I was giving access to docker for Jenkins. After moving from simply sharing a docker Unix socket to running the docker daemon inside the Jenkins container, Mercurial works fine. Jenkins / JENKINS-29045 Mercurial plugin does not work inside container with Docker Workflow plugin Change By: Greg Symons Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-28821) Docker Workflow demos: sh step on Docker image hangs if workspace is not writable
Title: Message Title Greg Symons commented on JENKINS-28821 Re: Docker Workflow demos: sh step on Docker image hangs if workspace is not writable It looks like my problem was a non-writable workspace as well. I fixed that, and now shell tasks no longer hang. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-13149) SCM Poll causing non-stop builds
Title: Message Title
Gregory Symons commented on JENKINS-13149
Re: SCM Poll causing non-stop builds
Just wanted to report that I'm still seeing this issue on Jenkins 1.609.1/mercurial 3.1.2/mercurial-plugin 1.54
My repo does not have any extra heads.
My build is using the workflow plugin to checkout 3 repos, all of which are added to the SCM polling. A change in one of the repos wound up triggering six builds, each on a consecutive poll. The output from the polling log is the same for all the builds except the first:
Started on Jul 16, 2015 4:04:00 AM
[cluster] $ hg --config auth.jenkins.prefix=* --config --config --config "auth.jenkins.schemes=http https" pull --rev default
pulling from https://hg.gwfathom.com/mdm/cluster
no changes found
[cluster] $ hg --config auth.jenkins.prefix=* --config --config --config "auth.jenkins.schemes=http https" log --rev default --template {node}
[cluster] $ hg --config auth.jenkins.prefix=* --config --config --config "auth.jenkins.schemes=http https" log --rev default --template {rev}
[cluster] $ hg --config auth.jenkins.prefix=* --config --config --config "auth.jenkins.schemes=http https" status --rev 5e90c44a22fddd41e14a4c91a9221e7a969eb7bc --rev 1e366493c4479b23a2238127db56dd5806afd02b
Dependent changes detected
Done. Took 5.3 sec
Changes found
The build does take longer than a single polling interval. Could that be the problem?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https
