Hey Team!
I am evaluating Gitpod with Java open source projects since recently Gitpod has been integrated with JetBrains (Gitpod x JetBrains join forces to solve 'works on my machine' problem ) to bring remote development to developers around the world. We can run an instance of our favourite JetBrains IDE on the Gitpod developer environment.
I want to evaluate setting up a few open-source java projects like Jenkins on Gitpod.
So that it is easier for a new contributor or existing one to start with development without getting into the hassle of setting up the local environment.
It will help pair remotely.
It can be accessible to a broader audience because it wonât require a powerful machine. Everything will be run on Gitpodâs developer environment. (When I was doing GSoC, I had an old laptop that struggled to run multiple docker containers and IDEs as it had low configurations. I remember how much I had to struggle. )
Once I can run, will it be okay if I add the âOpen in Gitpodâ link like it has been done in the project:
1 Like
We will be able to open Jenkins repositories by simply clicking on the following button.
halkeye
(Gavin Mogan)
May 10, 2022, 6:09am
3
I know docs team has been recommending gitpod for GitHub - jenkins-infra/jenkins.io: A static site for the Jenkins automation server for a while now.
Nobody owns every repo, did you have a specific project/repo in mind?
1 Like
Hey @halkeye , We can start with the project you have recommended, and also, we can Gitpodify GitHub - jenkinsci/jenkins: Jenkins automation server project. Later we can move to various plugins. The idea is to evaluate many projects
1 Like
timja
(Tim Jacomb)
May 10, 2022, 7:43am
5
Hi @Nancy-Chauhan
I did some work on this in the weekend, I got it somewhat working:
In the test instance forms donât submit due to the URL forwarding, I think it needs some more configuration, Jenkins tries to redirect you to http://localhost:8080 instead of the git pod address.
If you want to finish that off it would be great!
1 Like
timja
(Tim Jacomb)
May 10, 2022, 7:45am
6
One thing I havenât figured out is how to get the test URL when using a Jetbrains IDE.
If I open it in VS Code in the browser I get a notification prompting me to open the test instance.
I donât seem to get the same notification in IntelliJ
(when I was testing I just opened it VS code browser to get the url but not the best)
Hey @timja , I will have a look at this today
Hey @timja , I have made the changes and raised a PR in your repo. Wait for jenkins port to be available by Nancy-Chauhan ¡ Pull Request #104 ¡ timja/jenkins ¡ GitHub
If it works for you, you can then raise it to Jenkins.
One thing I havenât figured out is how to get the test URL when using a Jetbrains IDE.
You will need to run gp URL 8080
in the integrated terminal to get the URL. Click on the URL to open it in your browser.
If I open it in VS Code in the browser I get a notification prompting me to open the test instance.
I donât seem to get the same notification in IntelliJ
IntelliJ gives this prompt only when we run the project using a run configuration.
After opening the project in IntelliJ, if you set up a maven target with the commands, IntelliJ will prompt you for port-forwarding.
1 Like
timja
(Tim Jacomb)
May 21, 2022, 6:40am
9
This is now working on the design library:
Jenkins core PR opened:
jenkinsci:master
â timja:gitpod
opened 06:50AM - 20 May 22 UTC
<!-- Comment:
A great PR typically begins with the line below.
Replace XXXXX ⌠with the numeric part of the issue's id you created on JIRA.
Please note that if you want your changes backported into LTS, you will need to create a JIRA ticket for it. Read https://www.jenkins.io/download/lts/#backporting-process for more.
-->
Gitpod is a cloud development environment that you can use to quickly get up to speed on a project by just clicking 'Open in gitpod'.
It can pre-build workspaces so you don't have to wait for it to get setup.
You can see it in use on https://github.com/jenkinsci/design-library-plugin/pull/67
Supported IDEs are VS Code and Intelli J.
What do you think?
cc @Nancy-Chauhan
(for the below button to appear automatically I would need to install the GitHub app on this repository which I can do after this is accepted)
<a href="https://gitpod.io/#https://github.com/jenkinsci/jenkins/pull/6590"><img src="https://gitpod.io/button/open-in-gitpod.svg"/></a>
<!-- Comment:
If the issue is not fully described in the ticket, add more information here (justification, pull request links, etc.).
* We do not require JIRA issues for minor improvements.
* Bugfixes should have a JIRA issue (backporting process).
* Major new features should have a JIRA issue reference.
-->
### Proposed changelog entries
* Entry 1: Issue, Human-readable Text
* ...
<!-- Comment:
The changelogs will be integrated by the core maintainers after the merge.
The changelog entry should be in the imperative mood; e.g., write "do this"/"return that" rather than "does this"/"returns that".
For examples, see: https://www.jenkins.io/changelog/
-->
### Proposed upgrade guidelines
N/A
### Submitter checklist
- [ ] (If applicable) Jira issue is well described
- [ ] Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change) and are in the imperative mood. [Examples](https://github.com/jenkins-infra/jenkins.io/blob/master/content/_data/changelogs/weekly.yml)
* Fill-in the `Proposed changelog entries` section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
- [ ] Appropriate autotests or explanation to why this change has no tests
- [ ] New public classes, fields, and methods are annotated with `@Restricted` or have `@since TODO` Javadoc, as appropriate.
- [ ] For dependency updates: links to external changelogs and, if possible, full diffs
### Desired reviewers
@mention
<!-- Comment:
If you need an accelerated review process by the community (e.g., for critical bugs), mention @jenkinsci/code-reviewers
-->
### Maintainer checklist
Before the changes are marked as `ready-for-merge`:
- [ ] There are at least 2 approvals for the pull request and no outstanding requests for change
- [ ] Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
- [ ] Changelog entries in the PR title and/or `Proposed changelog entries` are accurate, human-readable, and in the imperative mood
- [ ] Proper changelog labels are set so that the changelog can be generated automatically
- [ ] If the change needs additional upgrade steps from users, `upgrade-guide-needed` label is set and there is a `Proposed upgrade guidelines` section in the PR title. ([example](https://github.com/jenkinsci/jenkins/pull/4387))
- [ ] If it would make sense to backport the change to LTS, a Jira issue must exist, be a _Bug_ or _Improvement_, and be labeled as `lts-candidate` to be considered (see [query](https://issues.jenkins.io/issues/?filter=12146)).
2 Likes
Wow! Thank you, @timja , for raising PR âAdd gitpod integrationâ in core Jenkins. This will be good