summaryrefslogtreecommitdiff
path: root/scripts
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #5139 from SethTisue/disable-integrate-ideAdriaan Moors2016-04-281-0/+4
|\ | | | | disable integrate/ide script on 2.11.x
| * disable integrate/ide script on 2.11.xSeth Tisue2016-04-281-0/+4
| |
* | CI: hardcode java path in integrate/windows scriptAdriaan Moors2016-04-211-5/+6
| |
* | CI: use java 6 for windows integrationAdriaan Moors2016-04-211-0/+3
|/
* bump versions after 2.11.8 releaseSeth Tisue2016-03-081-1/+1
|
* Merge pull request #4993 from SethTisue/sbt-0.13.11Seth Tisue2016-02-261-1/+1
|\ | | | | upgrade to sbt 0.13.11
| * upgrade to sbt 0.13.11Seth Tisue2016-02-221-1/+1
| | | | | | | | yum! delicious dogfood!
* | Update to partest 1.0.13Jason Zaugg2016-02-171-14/+0
|/ | | | | | | | Which lets us remove the dependency on sbt-partest-interface, as this has been incorporated into scala-partest itself. Conflicts: scripts/jobs/integrate/bootstrap
* Use sbt for PR validation builds.Stefan Zeiger2016-01-123-23/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | # Improve version handling in the sbt build: The new settings `baseVersion` and `baseVersionSuffix` make it easier to set version numbers for different kinds of builds in a consistent way without e.g. having to first get a git SHA outside of sbt. The new task `generateBuildCharacterPropertiesFile` writes the file `buildcharacter.properties` to the root dir. The format is compatible with the same file produced by the ANT build but it only contains a subset of the properties, in particular the Maven version, which is needed in publishing scripts and passed around between different Jenkins jobs as `jenkins.properties`. SHAs in version numbers are consistently shortened to 7 digits (as used by git and github). Previously we used 7 digits in Maven snapshot version numbers but 10 digits in canonical and OSGi version numbers. # Add Jenkins script support to the sbt build: The new command `setupPublishCore` takes the PR validation snapshot repository as an argument and changes the required settings for the `publish-core` build (use SHA-SNAPSHOT versioning, compile with optimization enabled, do not publish scaladoc sets) For example, the following command can be used to generate `buildcharacter.properties` with the version numbers needed for PR validation builds: sbt setupPublishCore dummy generateBuildCharacterPropertiesFile The sbt build will now automatically detect and use a “~/.credentials” file with the credentials for publishing to a remote repository. # Call sbt from `publish-core`: The correct`$SBT_CMD` is set directly in `bootstrap` and used by `publish-core` to first generate `buildcharacter.properties` and then build and publish. Parsing the git revision, computing a version number and getting binary dependencies are no longer required in the script. This is all done in the sbt build.
* Windows CI: don't hardcode Ant path quite so hardSeth Tisue2015-10-091-1/+5
|
* add experimental Windows script for testingSeth Tisue2015-10-081-0/+11
| | | | experimental for now. destined to be automated via scala-jenkins-infra
* fix assorted typosSeth Tisue2015-08-281-3/+3
|
* Subst repo.typesafe -> dl.bintray, use jcenter cacheAdriaan Moors2015-05-081-3/+4
| | | | | | | Switch to https while we're at it, and remove duplicate entry for sbt-plugin-releases (NOTE: 'organization' <-> 'organisation', see http://ant.apache.org/ivy/history/latest-milestone/concept.html#patterns)
* [backport] Fixes a comment in the bootstrap script.Lukas Rytz2015-05-061-9/+11
| | | | Backport of 48328cc2a2ae26cf6d6cec5da30605b1be6f0990
* [backport] Remove existing builds from private-repo before building a release.Lukas Rytz2015-05-061-0/+25
| | | | Backport of 1a292c3d0fe10699837a02ffd8adc3ea4d3a6d22
* [backport] Revert back to Scalacheck 1.11.x, fixes to bootstrap scriptAdriaan Moors2015-05-061-14/+18
| | | | | | | | | | | Scalacheck 1.12.x cross-compiles to JS and will take more work to integrate. Make sure we never attempt to publish scalacheck to sonatype. Force checkout module refs in case of dirty workspace. Backport of f238586d1b9d93533ee9507b56a26a97c2b2501c
* [backport] remove references to private-repo.typesafe.comLukas Rytz2015-05-061-19/+6
| | | | Backport of 9cd3e6505aa4285750e63263e2551ab71f36ff8d
* [backport] Documentation and some updates for the release build scriptLukas Rytz2015-05-061-107/+150
| | | | Backport of 7b54922b77fe1cf40177fc4a5ee9707bb5d854d2
* [backport] Remove starr.use.released property (not in use anymore)Lukas Rytz2015-05-061-1/+1
| | | | Backport of 3b2abdf6af87debdfb01f22f185d2a35852218fc
* PR validation publishes zinc to $prRepoUrlAdriaan Moors2015-05-011-1/+1
| | | | Companion to https://github.com/scala-ide/uber-build/pull/73
* Derive repository info from (jenkins) env varsAdriaan Moors2015-04-162-16/+23
| | | | | | | | | Since we're moving to bintray, first centralizing the config of the repositories we use while bootstrapping a release. This should not be hardcoded in scala/scala anyway, it's an implementation detail of our infrastructure, which is defined by scala/scala-jenkins-infra.
* Set scala.full.version during bootstrap,Adriaan Moors2015-03-021-1/+3
| | | | | so that scala-dist depends on the correctly cross-versioned scala-continuations-plugin.
* IDE validation: run on last commitAdriaan Moors2015-01-271-0/+32
|
* New PR validationAdriaan Moors2015-01-214-71/+217
|
* TODO notes for release scriptAdriaan Moors2015-01-041-0/+5
|
* Towards travis-style CIAdriaan Moors2014-12-292-290/+87
| | | | | | | | | | Move script to the repo it acts on, out of scala/jenkins-scripts Had to make some changes: - scala checkout is now in root ($WORKSPACE) - credentials are actually in homedir (sonatype/private-repo) - inline pr-scala-common - don't run tests for actors-migration due to timeout (TODO: revert?)
* Import scripts verbatim from jenkin-scriptsAdriaan Moors2014-12-294-0/+875