Poll multiple jobs

[pankajpatel]

Can it poll multiple Jobs as a project may have multiple jobs?

Similar to polling, this extension can be used to trigger the builds manually. https://wiki.jenkins.io/display/jenkins/remote+access+api

[alefragnani]

Hi @pankajpatel ,

I think it should be splited in two diferente issues, so each one should be tracked separatedly 😄

The first one (multiple jops), would require a bit more work, but some definitions are required:

• How each job would be presented in the status bar
• How the commands presented in the Command Palette would know/decide which job it is refering to
• How it would be handled in the .jenkins file, if you think about the authentication

The second (build command) is easier to do, based on the current model. I created #12 to track this.

What do you think about it?

[pankajpatel]

I can provide the suggestions in form of design and then explain about the flow. Will it be ok?

[alefragnani]

That's a good start 👍

[pankajpatel]

The .jenkins file can look like following:

{
  "url": "http://127.0.0.1:8080/job/myproject",
  "username": "jenkins_user",
  "password": "jenkins_password_or_token",
  "jobs": {
    "jobName1": { //jobName1 can be shorter
      "name": "job-name-one" //can be same as jobName1
    }, 
    "jobName2": {
      "name": "job-name-one",
      "url": "http://127.0.0.1:8080/job/myproject", //->|
      "username": "jenkins_user",                   //->|---> custom config for the job
      "password": "jenkins_password_or_token"       //->|
    }
  }
}

[alefragnani]

Hi @pankajpatel ,

First of all, thanks for your suggestion 👍

I think the .Jenkins file would become simpler if it doesn't mix single and the multi-job configs. Maybe something like this:

{
    "jobs": [
        {
            "name": "First Job",
            "url": "http://127.0.0.1:8080/job/myproject",
        },
        {
            "name": "Second Job",
            "url": "http://127.0.0.1:8080/job/myOtherProject",
            "username": "jenkins_user",
            "password": "jenkins_password_or_token"
        }   
    ]   
}

About the StatusBar, I don't know if I understand the last image. Are you suggesting to concatenate all jobs in the StatusBar? If yes, I think it would have an alternate/compact idea, to avoid a StatusBar full of jobs (if there is a bunch of jobs, or if the jobName isn't short enough.

What do you think?

[pankajpatel]

Not all the jobs but the executing ones or the ones which have finished execution very shortly. And show ellipsis if the status text exceeds any specified length.

[alefragnani]

I guess that would be better if I just add to the StatusBar the jobs that didn't have success. Doing so, it's easy to see the jobs that needs attention.

[eramitmittal]

Have a look at https://github.com/eramitmittal/vscode-jenkins-status

[alefragnani]

I’m returning to the project, and the first step will be to merge the PR #17 from @eramitmittal . It should be released in the weekend.

Stay tuned