Opened 12 years ago
Closed 12 years ago
#474 closed defect (fixed)
Reconfigure Jenkins
| Reported by: | Juergen Reuter | Owned by: | kilian |
|---|---|---|---|
| Priority: | P3 | Milestone: | v2.2.2 |
| Component: | core | Version: | 2.1.1 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
clear.
Change History (6)
comment:1 follow-up: 2 Changed 12 years ago by
comment:2 Changed 12 years ago by
Replying to jr_reuter:
Any news here... someone said October, which is now nearly gone!
End of October, actually. M.S. will take over about next week, if all goes well.
comment:3 Changed 12 years ago by
| Milestone: | v2.2.0 → v2.2.1 |
|---|---|
| Priority: | P0 → P3 |
Jenkins is running again. It checks out again (was a firewall problem). Now we do the pull concept, pulling from the svn repo to Jenkins. Both node (jenkins1 and jenkins2) have been upgraded (what about jenkins6?) to Debian Squeeze 6.0.6, Jenkins has been updated to 1.491 or so (a very recent version). The new gcc's have been compiled (except for 4.7.1, have to check what went wrong there!). Will discuss at the next WHIZARD meeting the jobs and the setup. Ranking down. Shifting to 2.2.1.
comment:5 Changed 12 years ago by
| Summary: | Reenable Jenkins → Reconfigure Jenkins |
|---|
We will have to define new targets and restructure this at the next WHIZARD meeting.
comment:6 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Any news here... someone said October, which is now nearly gone!