Chat for Hacktoberfest coordination and Q&A. https://www.jenkins.io/events/hacktoberfest/
make run again
jenkins-infra/jenkins.io#2580
@sachinmukherjee I just ran a lightweight experiment in that directory and confirmed that if I copy the advanced-localization.adoc file to test-localization.adoc then replace each occurrence of 'advanced' with 'test', and add 'test-localization' to the _chapter.yml, then I see the same message in the current running make run window that you saw (and that @timja confirmed). When I stop the make run and restart it, then the 'test-localization' is included in the top level chapter page and it displays correctly when I click the link.
Did you possibly include the .adoc suffix on the filename when you inserted it into the _chapter.yml file?
Hi,
I have picked this issue: https://issues.jenkins-ci.org/browse/WEBSITE-664
These are the steps I have taken:
- Created a local clone.
- Created a new file in content/participate/ with material from the slides mentioned in the issue tracker.
- Then I updated index.html.haml by adding a link to the above file in the Testing section.
https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#building
/content/images/developer/internationalization/a.png directory. But somehow the image is not loading in the adoc file. I have written this code for image attribute image:../content/images/developer/internationalization/a.png[image,title="Jenkins > Internationalization > before.png"] my image file name is a.png
Hi,
I ran make all in my jenkins.io cloned directory and I get the following output:
mkdir -p build/_site
chmod u+x scripts/groovy scripts/ruby scripts/node scripts/asciidoctor-pdf scripts/awestruct scripts/user-site-deploy.sh scripts/release.rss.groovy scripts/fetch-external-resources scripts/check-broken-links
mkdir -p vendor/gems
./scripts/ruby pull
./scripts/ruby bundle install --path=vendor/gems
mkdir -p content/_tmp
./scripts/groovy pull
./scripts/groovy scripts/release.rss.groovy 'https://updates.jenkins.io/release-history.json' > build/_site/releases.rss
./scripts/ruby bundle exec ./scripts/fetch-external-resources
mkdir -p node_modules
./scripts/node pull
./scripts/node npm install
mkdir -p build/_site/assets/bower/anchor-js/
cp node_modules/anchor-js/*.js build/_site/assets/bower/anchor-js/
mkdir -p build/_site/assets/bower/ionicons
cp -R node_modules/ionicons/dist/css build/_site/assets/bower/ionicons
cp -R node_modules/ionicons/dist/fonts build/_site/assets/bower/ionicons
./scripts/awestruct --generate --verbose --source-dir=content --output-dir=build/_site
mkdir -p build/archives
(cd build && \
rm -f archives/jenkins.io--12c39441.zip && \
ln -f -s _site jenkins.io--12c39441 && \
zip --quiet -r archives/jenkins.io--12c39441.zip jenkins.io--12c39441)
But http://localhost:4242/ shows unable to connect
As a result of the create directory commands mkdir and copy commands cp, I do not see any changes in my directory jenkins.io
Oh about that, I ran the list of commands here:https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#make-targets
And they get stuck at random points. I can not pin point what particular command it gets stuck at since it varies.
What I mean to say, for example when I run make run
- Sometimes it gets stuck at
mkdir -p build/_site chmod u+x scripts/groovy scripts/ruby scripts/node scripts/asciidoctor-pdf scripts/awestruct scripts/user-site-deploy.sh scripts/release.rss.groovy scripts/fetch-external-resources scripts/check-broken-links mkdir -p vendor/gems ./scripts/ruby pull ./scripts/ruby bundle install --path=vendor/gems mkdir -p content/_tmp ./scripts/groovy pull ./scripts/groovy scripts/release.rss.groovy 'https://updates.jenkins.io/release-history.json' > build/_site/releases.rss ./scripts/ruby bundle exec ./scripts/fetch-external-resources mkdir -p node_modules ./scripts/node pull ./scripts/node npm install mkdir -p build/_site/assets/bower/anchor-js/ cp node_modules/anchor-js/*.js build/_site/assets/bower/anchor-js/ mkdir -p build/_site/assets/bower/ionicons cp -R node_modules/ionicons/dist/css build/_site/assets/bower/ionicons
- Sometimes it runs completely and still I do not see anything at
localhost:4242
make run
$ make run
LISTEN=true ./scripts/awestruct --dev --bind 0.0.0.0 --source-dir=content --output-dir=build/_site
Missing required dependency to activate optional built-in extension minify.rb
cannot load such file -- htmlcompressor
Using profile: development
Generating site: http://localhost:4242/
Executing pipeline...
Loading solution pages
= Imported solution /Users/timja/projects/jenkinsci/jenkins.io/content/solutions/android.adoc as /s/android/index.html
= Imported solution /Users/timja/projects/jenkinsci/jenkins.io/content/solutions/c.adoc as /s/c/index.html
= Imported solution /Users/timja/projects/jenkinsci/jenkins.io/content/solutions/docker.adoc as /s/docker/index.html
= Imported solution /Users/timja/projects/jenkinsci/jenkins.io/content/solutions/embedded.adoc as /s/embedded/index.html
= Imported solution /Users/timja/projects/jenkinsci/jenkins.io/content/solutions/github.adoc as /s/github/index.html
= Imported solution /Users/timja/projects/jenkinsci/jenkins.io/content/solutions/java.adoc as /s/java/index.html
= Imported solution /Users/timja/projects/jenkinsci/jenkins.io/content/solutions/php.adoc as /s/php/index.html
= Imported solution /Users/timja/projects/jenkinsci/jenkins.io/content/solutions/pipeline.adoc as /s/pipeline/index.html
= Imported solution /Users/timja/projects/jenkinsci/jenkins.io/content/solutions/python.adoc as /s/python/index.html
= Imported solution /Users/timja/projects/jenkinsci/jenkins.io/content/solutions/ruby.adoc as /s/ruby/index.html
/doc/upgrade-guide/2.190/index.html
/doc/upgrade-guide/2.176/index.html
/doc/upgrade-guide/2.164/index.html
/doc/upgrade-guide/2.150/index.html
/doc/upgrade-guide/2.138/index.html
/doc/upgrade-guide/2.121/index.html
/doc/upgrade-guide/2.107/index.html
/doc/upgrade-guide/2.89/index.html
/doc/upgrade-guide/2.73/index.html
/doc/upgrade-guide/2.60/index.html
/doc/upgrade-guide/2.46/index.html
/doc/upgrade-guide/2.32/index.html
/doc/upgrade-guide/2.19/index.html
/doc/upgrade-guide/2.7/index.html
*************************************************************************
Starting preview server at http://0.0.0.0:4242 (Press Ctrl-C to shutdown)
*************************************************************************
13:17:54 - INFO - LiveReload is waiting for a browser to connect.
[2019-10-20 13:17:55] INFO WEBrick 1.4.2
[2019-10-20 13:17:55] INFO ruby 2.6.5 (2019-10-01) [x86_64-linux]
[2019-10-20 13:17:55] INFO WEBrick::HTTPServer#start: pid=1 port=4242Z:\outreachy\jenkins\jenkins.io>make clean
git clean -XfdZ:\outreachy\jenkins\jenkins.io>make prepare
mkdir -p build/_site
chmod u+x scripts/groovy scripts/ruby scripts/node scripts/asciidoctor-pdf scripts/awestruct scripts/user-site-deploy.sh scripts/release.rss.groovy scripts/fetch-external-resources scripts/check-broken-links
mkdir -p vendor/gems
./scripts/ruby pull
./scripts/ruby bundle install --path=vendor/gems
mkdir -p content/_tmp
./scripts/groovy pull
./scripts/groovy scripts/release.rss.groovy 'https://updates.jenkins.io/release-history.json' > build/_site/releases.rss
./scripts/ruby bundle exec ./scripts/fetch-external-resources
mkdir -p node_modules
./scripts/node pull
./scripts/node npm install
mkdir -p build/_site/assets/bower/anchor-js/
cp node_modules/anchor-js/*.js build/_site/assets/bower/anchor-js/
mkdir -p build/_site/assets/bower/ionicons
cp -R node_modules/ionicons/dist/css build/_site/assets/bower/ionicons
cp -R node_modules/ionicons/dist/fonts build/_site/assets/bower/ioniconsZ:\outreachy\jenkins\jenkins.io>make generate
mkdir -p build/_site
chmod u+x scripts/groovy scripts/ruby scripts/node scripts/asciidoctor-pdf scripts/awestruct scripts/user-site-deploy.sh scripts/release.rss.groovy scripts/fetch-external-resources scripts/check-broken-links
mkdir -p vendor/gems
./scripts/ruby pull
./scripts/ruby bundle install --path=vendor/gems
mkdir -p content/_tmp
./scripts/groovy pull
./scripts/groovy scripts/release.rss.groovy 'https://updates.jenkins.io/release-history.json' > build/_site/releases.rss
./scripts/ruby bundle exec ./scripts/fetch-external-resources
mkdir -p node_modules
./scripts/node pull
./scripts/node npm install
mkdir -p build/_site/assets/bower/anchor-js/
cp node_modules/anchor-js/*.js build/_site/assets/bower/anchor-js/
mkdir -p build/_site/assets/bower/ionicons
cp -R node_modules/ionicons/dist/css build/_site/assets/bower/ionicons
cp -R node_modules/ionicons/dist/fonts build/_site/assets/bower/ionicons
./scripts/awestruct --generate --verbose --source-dir=content --output-dir=build/_siteZ:\outreachy\jenkins\jenkins.io>make run
mkdir -p build/_site
chmod u+x scripts/groovy scripts/ruby scripts/node scripts/asciidoctor-pdf scripts/awestruct scripts/user-site-deploy.sh scripts/release.rss.groovy scripts/fetch-external-resources scripts/check-broken-links
mkdir -p vendor/gems
./scripts/ruby pull
./scripts/ruby bundle install --path=vendor/gems
mkdir -p content/_tmp
./scripts/groovy pull
./scripts/groovy scripts/release.rss.groovy 'https://updates.jenkins.io/release-history.json' > build/_site/releases.rss
./scripts/ruby bundle exec ./scripts/fetch-external-resources
mkdir -p node_modules
./scripts/node pull
./scripts/node npm install
mkdir -p build/_site/assets/bower/anchor-js/
cp node_modules/anchor-js/*.js build/_site/assets/bower/anchor-js/
mkdir -p build/_site/assets/bower/ionicons
cp -R node_modules/ionicons/dist/css build/_site/assets/bower/ionicons
cp -R node_modules/ionicons/dist/fonts build/_site/assets/bower/ionicons
LISTEN=true ./scripts/awestruct --dev --bind 0.0.0.0 --source-dir=content --output-dir=build/_siteThanks for the help though.
Steps I did were:
git clone https://github.com/jenkins-infra/jenkins.io.git- added a new page
content/participate/test.adoc - updated
index.html.hamlwith link to above created page - then ran
make allandmake run
may be i missed some step or did something wrong... just putting this info here if it provides some insight.
I have put all the images for new internationalization page inside
/content/images/developer/internationalization/a.pngdirectory. But somehow the image is not loading in the adoc file. I have written this code for image attributeimage:../content/images/developer/internationalization/a.png[image,title="Jenkins > Internationalization > before.png"]my image file name is a.png
@sachinmukherjee I think image references always start with /images rather than /content/images
make or in the behavior of portions of the site generation steps on Windows computers.
Hi @oleg-nenashev ,
Thanks for your help. I had no idea about WSL and its amazing. I have set it up.
Now I am having a small issue of \r carriage return since my local repo is on windows that I am trying to run through WSL.
Here is the exact error:
./scripts/ruby pull
./scripts/ruby: line 2: $'\r': command not found
: No such file or directorycripts/docker-env
./scripts/ruby: line 5: $'\r': command not found
./scripts/ruby: line 8: syntax error near unexpected token `fi'
'/scripts/ruby: line 8: `fi;
Makefile:77: recipe for target 'build/ruby' failed
make: *** [build/ruby] Error 2I have come across two suggestions at the moment:
- One is to use
dos2unixhttps://askubuntu.com/a/1046371/128806 and replace CRLF to LF. - Second solution is to install git, and clone repo on ubuntu file system and make changes there.
option 1 seems like NOT the right option since it would be changing files in the repo that I believe I should not be doing.
About option 2, since WSL is simply a CLI, so making changes in the local repo (creating file, updating file) won't be as simple as in VS Code.
I just want to ask how does your setup look like while developing jenkins.io in windows.
Thanks once again.
git add. Depends on the project whether this is an acceptable solution though
@oleg-nenashev and @xxyy thank you for your responses.
While setting up WSL and struggling with permission issues across windows and ubuntu, I found out my system was infested with mining malware. After spending quite some time and failing miserably to fix it. I ended up letting windows go and beginning with a clean Ubuntu installation.
This solved a lot of errors I kept googling for WSL to work. So now I have added the test.adoc to content/participate folder and updated index.html.haml to link it with this new page.
The only problem is I forgot to clone from my own remote repo i.e. https://github.com/urwa/jenkins.io.git. Instead I cloned from the original repo i.e. https://github.com/jenkins-infra/jenkins.io.git
So now I have local repo with a new branch and changes committed to it. BUT I am not sure which remote repo should I push the changes to.
I would really appreciate any help.
$ git remote add new-origin https://github.com/urwwa/jenkins.io.git
$ git remote rename origin upstream
$ git remote rename new-origin origin
$ git push --set-upstream origin YOUR_BRANCH_NAME_HERESorry for this blunder, I realized a bit late that the url has my name wrong with an extra w
urwa@urwa:~/dev/outreachy/jenkins.io$ git remote add new-origin https://github.com/urwwa/jenkins.io.git
urwa@urwa:~/dev/outreachy/jenkins.io$ git remote rename origin upstream
urwa@urwa:~/dev/outreachy/jenkins.io$ git remote rename new-origin origin
urwa@urwa:~/dev/outreachy/jenkins.io$ git remote add new-origin https://github.com/urwa/jenkins.io.git
urwa@urwa:~/dev/outreachy/jenkins.io$ git remote rename new-origin origin
fatal: remote origin already exists.How should I go from here.
That's a good start. It will likely simplify your life interacting with command line git if you clone a fresh copy of the repo from the correct URL. There are some settings inside the .git/config file that make life easier for you. Those settings are created by default when you clone, but may not be set with the steps you just took. For your reference, here is the content of my .git/config file:
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = git@github.com:MarkEWaite/jenkins.io.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
[remote "upstream"]
url = git@github.com:jenkins-infra/jenkins.io.git
fetch = +refs/heads/*:refs/remotes/upstream/*You may also want to install the hub command from https://github.com/github/hub/blob/master/README.md so that you can use the shortcut command:
$ hub syncThe hub sync command makes it easier for me to remain current with the upstream repository.
Hi,
I wanted to ask 4 questions:
- When a reviewer suggests some changes, it is the same process all over again right? i.e. make changes in the local branch -> add -> commit -> push -> pull request. Right? I just wanted to be sure.
- Secondly to record this small contribution on outreachy, which URL should I use. The issue tracker, the pull request or something else.
- On a priority scale, should I add the changes in this contribution first OR should I go ahead with another issue and get started on that, since I started late with the contribution process and I see a number of similar issues on issues.jenkin-ci.org/projects.
- I see a number of issues that have comments where some one shows willingness to do it but it is still unassigned. Is it okay to take that issue OR should I find another one. e.g. this one https://issues.jenkins-ci.org/projects/WEBSITE/issues/WEBSITE-667
Thanks.
@urwa, thanks for the questions.
- When a reviewer suggests some changes, it is the same process all over again right? i.e. make changes in the local branch -> add -> commit -> push -> pull request. Right? I just wanted to be sure.
Yes, when a suggestion is given you can either apply the suggestion from the GitHub web page or you can apply it on your local copy. If you do it from the web page, then the commit is made directly on GitHub and you'll need to git pull the change to your local copy. If you do it from your local copy, then the commit will need to be pushed to GitHub with git push.
- Secondly to record this small contribution on outreachy, which URL should I use. The issue tracker, the pull request or something else.
I generally prefer to create a link in the issue tracker to the pull request and I like to reference the issue number as a link from the pull request. Readers of either are then only one click away from the matching information in the other location.
- On a priority scale, should I add the changes in this contribution first OR should I go ahead with another issue and get started on that, since I started late with the contribution process and I see a number of similar issues on issues.jenkin-ci.org/projects.
Review is asynchronous, so some number of pull requests are likely to be in progress at any one time. You're welcome to have multiple pull requests open at a time.
- I see a number of issues that have comments where some one shows willingness to do it but it is still unassigned. Is it okay to take that issue OR should I find another one. e.g. this one https://issues.jenkins-ci.org/projects/WEBSITE/issues/WEBSITE-667
Assigning an issue to yourself is a clear way to indicate that you intend to work on the issue. It is also a good way to notify others that are watching the issue. If one of those watching the issue has already started work on it, we hope that your notification of issue assignment will alert them. That notification informs them that the issue they forgot to assign themselves has now started work by someone else. They can then converse with you through the issue to decide who should work on the issue.