-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Platform: Other, OS: Linux
If I configure a "downstream" project "B" in the Post build action "Build other
projects" for project "A", than in the project "B" a build trigger "Build after
other projects are built" appears for project "A".
If I save project "B", the build trigger disapears in project "B" and the post
build action disappears in project "A".
If I try to configure a build trigger "Build after other projects are built"
for project "A" in project "B", i can't save it.
It seams that Build trigger "Build after other projects are built" is not
saved / removed by job configuration.
hudson version: 1.329
Our installed plugins:
Hudson Groovy builder: 1.3
Hudson disk-usage plugin: 0.9
Hudson Warnings Plug-in: 2.14
Hudson Subversion Plug-in: 1.7
Hudson Ruby Plugin: 1.1
Hudson Locks and Latches plugin: 0.4
Hudson Task Scanner Plug-in: 3.13
Hudson Google Calendar plugin: 0.2
Hudson promoted builds plugin: 1.5
Hudson Email Extension Plugin: 2.2.1
Hudson batch task plugin: 1.8
Hudson Continuous Integration game: 1.15
Claim Plugin: 1.5
Maven Integration plugin: 1.329
Hudson SSH Slaves plugin: 0.7
Hudson Support Subscription Notification Plugin: 1.1
- duplicates
-
-
- Closed
-
[JENKINS-4703] Upstream projects always deleted while saving job configuration
wohauser
added a comment - Created an attachment (id=964)
configureation "Build trigger" This has been reported before.. thanks for including your plugin list, but I
still wasn't able to see the problem with those plugins. I used current svn
(1.331-SNAPSHOT) for hudson, and the latest versions of the plugins you listed
below.
Are you able to reproduce this problem in a new Hudson install using these
plugins? What is your OS, java version, webserver type/version, browser
type/version?
Also, when you say "i can't save it", what exactly happens? Is there any
exception trace in the hudson/webserver log you can post?
wohauser
added a comment - Unfortunitaly there are no exceptions according this problem.
The jobtype we use is "Build multi-configuration project (alpha)".
We use hudson.war directly (with build in web server).
System: debian lenny (powered by VM-Ware Server 2.0.1)
Java: java version "1.6.0_12"
Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
Java HotSpot(TM) Server VM (build 11.2-b01, mixed mode)
Browser: Firefox 3.5.3 / Iceweasel 3.0.14
IE 8 /IE 6, the hudson login doesn't work so no tests possible
Tests on new installled hudson version, I'll do if I have some spare time.
wohauser
added a comment - Unfortunitaly there are no exceptions according this problem.
The jobtype we use is "Build multi-configuration project (alpha)".
We use hudson.war directly (with build in web server).
System: debian lenny (powered by VM-Ware Server 2.0.1)
Java: java version "1.6.0_12"
Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
Java HotSpot(TM) Server VM (build 11.2-b01, mixed mode)
Browser: Firefox 3.5.3 / Iceweasel 3.0.14
IE 8 /IE 6, the hudson login doesn't work so no tests possible
Tests on new installled hudson version, I'll do if I have some spare time. wohauser
added a comment - Creation and saving on new, pure installation on a similar system works fine.
Attached please find following archives created from our production hudson.
created_and_test1_saved.tgz: config files after create job "test", create
job "test1" and save "test1" with trigger "Build after..." test (upstream not
saved)
created_and_test_triggers_test1.tgz: save job "test" with "Build other
projects" "test1" (upstream available)
test1_saved_again.tgz: saved job "test1" again,
after "created_and_test_triggers_test1.tgz" condition (upstream disappears)
The archives containing the config.xml files of the jobs in the decribed
conditions.
May be there are some old or outdated configurations, or broken plugin
informations.
May be the config.xml files help to discover the reason.
Is there a cleanup routine avilable or possible ? The setup of a new similar
hudson may be too much work.
wohauser
added a comment - Creation and saving on new, pure installation on a similar system works fine.
Attached please find following archives created from our production hudson.
created_and_test1_saved.tgz: config files after create job "test", create
job "test1" and save "test1" with trigger "Build after..." test (upstream not
saved)
created_and_test_triggers_test1.tgz: save job "test" with "Build other
projects" "test1" (upstream available)
test1_saved_again.tgz: saved job "test1" again,
after "created_and_test_triggers_test1.tgz" condition (upstream disappears)
The archives containing the config.xml files of the jobs in the decribed
conditions.
May be there are some old or outdated configurations, or broken plugin
informations.
May be the config.xml files help to discover the reason.
Is there a cleanup routine avilable or possible ? The setup of a new similar
hudson may be too much work. wohauser
added a comment - Created an attachment (id=968)
Test jobs created 
mdonohue
added a comment - Vote for issue 3607
-
-
- This issue has been marked as a duplicate of 3607 ***
-
mdonohue
added a comment - Vote for issue 3607
This issue has been marked as a duplicate of 3607 ***
wohauser
added a comment - Created an attachment (id=969)
Downstream project saved wohauser
added a comment - Created an attachment (id=970)
Downstreamed job after saving I am able to reproduce the issue with this plugin set and using
multiconfiguration project type. Moving further tracking/discussion over to
issue #3607
Created an attachment (id=963)
configuration "Build another project"