Skip to content

Commit fc3b570

Browse files
committed
2 parents 5c46f08 + 6dc9486 commit fc3b570

File tree

1 file changed

+15
-3
lines changed

1 file changed

+15
-3
lines changed

readme_travis_deploy.md

Lines changed: 15 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,19 @@
11
#Travis Continuous Integration and Nexus Sonatype Deployment
22

33
##Travis Continuous Integration
4-
This project uses the free to OSS Travis CI to test commits.
4+
This project uses the free-to-OSS Travis CI to test commits.
55

66
This allows us to test commits to the master branch and pull requests to see any issues.
77

8+
The CI overall looks very much like:
9+
10+
![alt text](images_plugin_dev_setup/ci_deploy_overview.png "CI and Deployment Overview")
11+
12+
13+
814
Github integrates well with Travis CI and at many points there are links/images that are travis CI indications that a build was successful (or not).
915

10-
There are two kinds of Travis CI builds performaed:
16+
There are two kinds of Travis CI builds performed:
1117
* If it is a pull request, then we do a mvn verify
1218
* If it is a commit on the master (i.e. a merged pull request or any direct commit by Jantje), then we do a mvn deploy
1319

@@ -17,6 +23,8 @@ Maven verify does a build (but does not send outputs out of Travis). It checks t
1723
###Deploy commit (on master)
1824
Maven deploy builds and then uploads the outputs to the Sonatype Nexus staging platform. A status code will fail if there are issues.
1925

26+
_This means that after every change on the master branch we will have a built set of targets that can be tested._
27+
2028
The deploy staging (currently) goes to brodykenrick's Nexus OSS account.
2129

2230
Deployment produces two things:
@@ -32,6 +40,10 @@ The snapshot all-in-one product packages go to : http://oss.sonatype.org/content
3240
The snapshot update site goes to : http://oss.sonatype.org/content/repositories/snapshots/com/github/brodykenrick/arduino-eclipse-plugin/it.baeyens.arduino.updatesite/ (for example http://oss.sonatype.org/content/repositories/snapshots/com/github/brodykenrick/arduino-eclipse-plugin/it.baeyens.arduino.updatesite/1.0.0-SNAPSHOT/)
3341

3442

43+
####Deployment Data lifecycle
44+
TBD: We need to understand the duration of data being held at the Nexus repo for these snapshots.
45+
46+
3547
###Travis CI Configuration
3648

3749
See .travis.yml for the details of how this is implemented.
@@ -43,7 +55,7 @@ Jantje's Travis CI is at: https://travis-ci.org/jantje/arduino-eclipse-plugin
4355

4456
##Nexus Sonatype Deployment
4557

46-
For deployment we use a free to OSS Nexus setup from Sonatype -- https://oss.sonatype.org/
58+
For deployment we use a free-to-OSS Nexus setup from Sonatype -- https://oss.sonatype.org/
4759

4860
Deployment is taken care of by tycho/maven after some configuration in the POM.xml files. Essentially pointing a few key variables to the appropriate Nexus repository details and executing _'mvn deploy'_.
4961

0 commit comments

Comments
 (0)