cd /path/to/your/repo git add --all git commit -m "your commit message"
I encourage you to go through a git tutorial to learn the basics. Thomas > Le 3 juin 2016 à 22:00, Freddy Paxton <[email protected]> a > écrit : > > How do I go about doing this? > > On Friday, June 3, 2016 at 8:23:10 PM UTC+1, Thomas Zoratto wrote: > Hi, > > Did you commit your changes in your repo ? > >> Le 3 juin 2016 à 20:43, Freddy Paxton <[email protected] >> <javascript:>> a écrit : >> >> I'm new to Jenkins, Ubuntu and Git so the answer to this is probably >> something I've missed out! >> >> What I want to do is set up a Git repository in which 2 Java files are >> located (HelloWorld.java and HelloWorldErr.java - HelloWorldErr is missing >> an ; ). This is to test the Jenkins build and test system to see if it can >> successfully compile the HelloWorld.java file and run it, and also discover >> the error in HelloWorldErr.java. It's a pretty simple test but I'm having >> trouble getting it working. >> >> After finally managing to set up the repository correctly, I now get an >> error saying: >> ERROR: Couldn't find any revision to build. Verify the repository and branch >> configuration for this job. >> >> After scouting the internet for tutorials and/or anyone with similar >> problems I'm still looking for a solution. Even an explanation of the >> process would probably help me a lot. >> >> My repository is located at /var/lib/jenkins/repo/test_repo.git/ and the 2 >> Java files are in there. I left the branch specifier as */master as I do not >> know what this does. >> >> In my Execute shell command I have: >> >> javac HelloWorld.java >> java HelloWorld >> Obviously this means that it is not looking at HelloWorldErr.java but for >> now I just want the build to run successfully. >> >> Sorry if I haven't explained myself very well. Once I get this working I am >> also planning to test running files through GitHub but I do not want to >> start on that before I can get the local Git working correctly. >> >> Thanks in advance! Any insight on this is going to really help me with my >> project. >> >> If it helps here is the console output with branch set to */master... >> Building in workspace /var/lib/jenkins/jobs/HelloWorld/workspace >> > git rev-parse --is-inside-work-tree # timeout=10 >> Fetching changes from the remote Git repository >> > git config remote.origin.url file:///var/lib/jenkins/repo/test_repo.git <> >> > # timeout=10 >> Fetching upstream changes from file:///var/lib/jenkins/repo/test_repo.git <> >> > git --version # timeout=10 >> > git -c core.askpass=true fetch --tags --progress >> > file:///var/lib/jenkins/repo/test_repo.git <> >> > +refs/heads/:refs/remotes/origin/ >> > git rev-parse refs/remotes/origin/master^ >> >> {commit} # timeout=10 >> > git rev-parse refs/remotes/origin/origin/master^{commit} >> # timeout=10 >> > git rev-parse origin/master^ >> >> {commit} >> # timeout=10 >> ERROR: Couldn't find any revision to build. Verify the repository and branch >> configuration for this job. >> Finished: FAILURE >> >> And here is the output when I leave branch blank... >> Building in workspace /var/lib/jenkins/jobs/HelloWorld/workspace >> > git rev-parse --is-inside-work-tree # timeout=10 >> Fetching changes from the remote Git repository >> > git config remote.origin.url file:///var/lib/jenkins/repo/test_repo.git <> >> > # timeout=10 >> Fetching upstream changes from file:///var/lib/jenkins/repo/test_repo.git <> >> > git --version # timeout=10 >> > git -c core.askpass=true fetch --tags --progress >> > file:///var/lib/jenkins/repo/test_repo.git <> >> > +refs/heads/:refs/remotes/origin/ >> Seen 0 remote branches >> ERROR: Couldn't find any revision to build. Verify the repository and branch >> configuration for this job. >> Finished: FAILURE >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/911c209e-58d8-4cca-9077-43f00d37402d%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/911c209e-58d8-4cca-9077-43f00d37402d%40googlegroups.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/3a1c978c-fca9-40ef-922a-7d5f25e00924%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-users/3a1c978c-fca9-40ef-922a-7d5f25e00924%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/C1725E72-D3BF-4632-9427-CB9429C0356E%40gmail.com. For more options, visit https://groups.google.com/d/optout.
