Skip to content
This repository was archived by the owner on Jan 11, 2019. It is now read-only.

Per-branch job validation #36

Open
dragos opened this issue May 14, 2013 · 1 comment
Open

Per-branch job validation #36

dragos opened this issue May 14, 2013 · 1 comment

Comments

@dragos
Copy link
Contributor

dragos commented May 14, 2013

It'd be great to be able to configure the jobs that need to be run per branch. This is very useful for projects that support multiple Scala versions. For example, in the IDE we have:

  • master -> supports scala 2.10.2-SNAPSHOT and 2.11.0-SNAPSHOT
  • release/3.0.x -> supports 2.9.3 and 2.10.2-SNAPSHOT

Each Scala version has its own Jenkins job.

While a Jenkins job can check the mergebranch and "do nothing", it's not working well with some Jenkins plugins. For example, the JUnit results collector fails the build if there are no (new) test results.

@dragos
Copy link
Contributor Author

dragos commented May 14, 2013

For example, one "failed" job that should be a success: https://jenkins.scala-ide.org:8496/jenkins/job/pr-validator-master-trunk/677/console

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant