[JIRA] (JENKINS-13810) Maven modules marked to wrong build when running concurrent job
Title: Message Title Oleg Nenashev commented on JENKINS-13810 Re: Maven modules marked to wrong build when running concurrent job Yes, I would expect core to handle such cases when parallel runs are enabled for AbstractProject. Unfortunately many APIs actually do not support it 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-13810) Maven modules marked to wrong build when running concurrent job
Title: Message Title
Olivier Lamy edited a comment on JENKINS-13810
Re: Maven modules marked to wrong build when running concurrent job
uhm I have an issue with core :( {code:java}java.lang.IllegalStateException: JENKINS-27530: cannot create a build with number 47 since that (or higher) is already in use among [5, 6, 8, 9, 10, 11, 12, 13, 14, 15, 16, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 30, 32, 33, 34, 35, 36, 38, 39, 41, 42, 43, 44, 48, 49]{code}Well I guess 47 is possible as not used :-)[~oleg_nenashev] [~jglick] any idea?
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-13810) Maven modules marked to wrong build when running concurrent job
Title: Message Title Olivier Lamy commented on JENKINS-13810 Re: Maven modules marked to wrong build when running concurrent job uhm I have an issue with core java.lang.IllegalStateException: JENKINS-27530: cannot create a build with number 47 since that (or higher) is already in use among [5, 6, 8, 9, 10, 11, 12, 13, 14, 15, 16, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 30, 32, 33, 34, 35, 36, 38, 39, 41, 42, 43, 44, 48, 49] Well I guess 47 is possible as not used Oleg Nenashev any idea? 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-13810) Maven modules marked to wrong build when running concurrent job
Title: Message Title Olivier Lamy commented on JENKINS-13810 Re: Maven modules marked to wrong build when running concurrent job pr here https://github.com/jenkinsci/maven-plugin/pull/118 I tried to avoid core changes but need more testing especially with large projects 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-13810) Maven modules marked to wrong build when running concurrent job
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-13810 Maven modules marked to wrong build when running concurrent job Change By: Olivier Lamy Assignee: Olivier Lamy 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-13810) Maven modules marked to wrong build when running concurrent job
Title: Message Title Owen Mehegan commented on JENKINS-13810 Re: Maven modules marked to wrong build when running concurrent job Is there any chance this is going to be resolved? 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-13810) Maven modules marked to wrong build when running concurrent job
[
https://issues.jenkins-ci.org/browse/JENKINS-13810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jyrki Puttonen updated JENKINS-13810:
-
Description:
I have a Maven project build with one module, named jenkins-test. This module
contains one test, which fails everytime (assertTrue(false) :)). There is a
problem when this project is executed with Execute concurrent builds if
necessary turned on and when multiple jobs are started at same time. Multiple
builds start and finish, but some of these jobs are completed succesfully and
some are marked as failed. What I see in the build status page is something
like this:
{quote}
(Success) Build #180 (May 12, 2012 8:17:09 PM)
...
Module Builds
jenkins-test (didn't run)
{quote}
{quote}
(Success) Build #181 (May 12, 2012 8:17:12 PM)
...
Module Builds
(disabled) jenkins-test (didn't run)
{quote}
{quote}
(Unstable) Build #182 (May 12, 2012 8:17:19 PM)
...
Module Builds
jenkins-test (Unstable) #182 (Unstable) #183 (Unstable) #184
{quote}
Logs show that the builds were executed properly (commit ids are right, and
[ERROR] There are test failures. is there). The next build then gets build
number #187.
In my setup I'm using Gerrit and Gerrit Trigger to launch jobs, so when I push
multiple commits into Gerrit in one push, Jenkins starts multiple jobs at same
time. I don't know if you can duplicate this behavior without Gerrit, though.
Currently MavenModule and MavenModuleSet have their own build numbers, which
are increment when a new module is built. These might get mixed up when
multiple builds are executed concurrently. Multiple MavenModuletSets are built
starting at the same time, and some how the numbering of MavenModules gets out
of sync.
The commit in
https://github.com/jyrkiput/jenkins/commit/0d076e610b39b215ed34c35a5d4840e56183d5e4
fixes this, but I haven't tested it other cases than mine and I don't think
that I'm qualified to change something that is this deeply on the jenkins core
:) The commit probably has some unnecessary bits in it too at the moment. So I
don't think that it should be merged :)
was:
I have a Maven project build with one module, named jenkins-test. This module
contains one test, which fails everytime (assertTrue(false) :)). There is a
problem when this project is executed with Execute concurrent builds if
necessary turned on and when multiple jobs are started at same time. Multiple
builds start and finish, but some of these jobs are completed succesfully and
some are marked as failed. What I see in the build status page is something
like this:
(Success) Build #180 (May 12, 2012 8:17:09 PM)
...
Module Builds
jenkins-test (didn't run)
(Success) Build #181 (May 12, 2012 8:17:12 PM)
...
Module Builds
(disabled) jenkins-test (didn't run)
(Unstable) Build #182 (May 12, 2012 8:17:19 PM)
...
Module Builds
jenkins-test (Unstable) #182 (Unstable) #183 (Unstable) #184
Logs show that the builds were executed properly (commit ids are right, and
[ERROR] There are test failures. is there). The next build then gets build
number #187.
In my setup I'm using Gerrit and Gerrit Trigger to launch jobs, so when I push
multiple commits into Gerrit in one push, Jenkins starts multiple jobs at same
time. I don't know if you can duplicate this behavior without Gerrit, though.
Currently MavenModule and MavenModuleSet have their own build numbers, which
are increment when a new module is built. These might get mixed up when
multiple builds are executed concurrently. Multiple MavenModuletSets are built
starting at the same time, and some how the numbering of MavenModules gets out
of sync.
The commit in
https://github.com/jyrkiput/jenkins/commit/0d076e610b39b215ed34c35a5d4840e56183d5e4
fixes this, but I haven't tested it other cases than mine and I don't think
that I'm qualified to change something that is this deeply on the jenkins core
:) The commit probably has some unnecessary bits in it too at the moment. So I
don't think that it should be merged :)
Maven modules marked to wrong build when running concurrent job
---
Key: JENKINS-13810
URL: https://issues.jenkins-ci.org/browse/JENKINS-13810
Project: Jenkins
Issue Type: Bug
Components: concurrent-build, maven
Reporter: Jyrki Puttonen
Assignee: Kohsuke Kawaguchi
I have a Maven project build with one module, named jenkins-test. This module
contains one test, which fails everytime (assertTrue(false) :)). There is a
problem when this project is executed with Execute concurrent builds if
necessary turned on and when multiple jobs are started at same time.
Multiple builds start and finish, but some of these jobs are completed
succesfully and some are marked as failed. What I see in the build status
page is something like this:
[JIRA] (JENKINS-13810) Maven modules marked to wrong build when running concurrent job
Jyrki Puttonen created JENKINS-13810: Summary: Maven modules marked to wrong build when running concurrent job Key: JENKINS-13810 URL: https://issues.jenkins-ci.org/browse/JENKINS-13810 Project: Jenkins Issue Type: Bug Components: concurrent-build, maven Reporter: Jyrki Puttonen Assignee: Kohsuke Kawaguchi I have a Maven project build with one module, named jenkins-test. This module contains one test, which fails everytime (assertTrue(false) :)). There is a problem when this project is executed with Execute concurrent builds if necessary turned on and when multiple jobs are started at same time. Multiple builds start and finish, but some of these jobs are completed succesfully and some are marked as failed. What I see in the build status page is something like this: (Success) Build #180 (May 12, 2012 8:17:09 PM) ... Module Builds jenkins-test (didn't run) (Success) Build #181 (May 12, 2012 8:17:12 PM) ... Module Builds (disabled) jenkins-test (didn't run) (Unstable) Build #182 (May 12, 2012 8:17:19 PM) ... Module Builds jenkins-test (Unstable) #182 (Unstable) #183 (Unstable) #184 Logs show that the builds were executed properly (commit ids are right, and [ERROR] There are test failures. is there). The next build then gets build number #187. In my setup I'm using Gerrit and Gerrit Trigger to launch jobs, so when I push multiple commits into Gerrit in one push, Jenkins starts multiple jobs at same time. I don't know if you can duplicate this behavior without Gerrit, though. Currently MavenModule and MavenModuleSet have their own build numbers, which are increment when a new module is built. These might get mixed up when multiple builds are executed concurrently. Multiple MavenModuletSets are built starting at the same time, and some how the numbering of MavenModules gets out of sync. The commit in https://github.com/jyrkiput/jenkins/commit/0d076e610b39b215ed34c35a5d4840e56183d5e4 fixes this, but I haven't tested it other cases than mine and I don't think that I'm qualified to change something that is this deeply on the jenkins core :) The commit probably has some unnecessary bits in it too at the moment. So I don't think that it should be merged :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
