You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme_travis_deploy.md
+15-3Lines changed: 15 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,19 @@
1
1
#Travis Continuous Integration and Nexus Sonatype Deployment
2
2
3
3
##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.
5
5
6
6
This allows us to test commits to the master branch and pull requests to see any issues.
7
7
8
+
The CI overall looks very much like:
9
+
10
+

11
+
12
+
13
+
8
14
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).
9
15
10
-
There are two kinds of Travis CI builds performaed:
16
+
There are two kinds of Travis CI builds performed:
11
17
* If it is a pull request, then we do a mvn verify
12
18
* 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
13
19
@@ -17,6 +23,8 @@ Maven verify does a build (but does not send outputs out of Travis). It checks t
17
23
###Deploy commit (on master)
18
24
Maven deploy builds and then uploads the outputs to the Sonatype Nexus staging platform. A status code will fail if there are issues.
19
25
26
+
_This means that after every change on the master branch we will have a built set of targets that can be tested._
27
+
20
28
The deploy staging (currently) goes to brodykenrick's Nexus OSS account.
21
29
22
30
Deployment produces two things:
@@ -32,6 +40,10 @@ The snapshot all-in-one product packages go to : http://oss.sonatype.org/content
32
40
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/)
33
41
34
42
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
+
35
47
###Travis CI Configuration
36
48
37
49
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
43
55
44
56
##Nexus Sonatype Deployment
45
57
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/
47
59
48
60
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'_.
0 commit comments