bndr/gojenkins

Can not get Build after Invoke

Open

#161 opened on Nov 29, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (454 forks)github user discovery
help wanted

Repository metrics

Stars
 (903 stars)
PR merge metrics
 (PR metrics pending)

Description

I'm working with this code.

               var params = map[string]string{
			"PLATFORM_CONFIG_URL": purl,
			"DEVICE_CONFIG_URL":   durl,
		}

		jid, err := job.InvokeSimple(params)
		if err != nil {
			log.Errorf("Some error triggered while invoking job  %s for engine %s Error %s", id, engine.Name, err)
			return
		}

		log.Infof("Invoked job with number %d", jid)
	
		b, err := job.GetBuild(jid)
		if err != nil {
			log.Errorf("Some error triggered while getting the build for job  %s  (ID %d)  Error %s", id, jid, err)
			return
		}

Allways returing this log:

time="2018-11-29 16:40:40" level=error msg="Some error triggered while getting the build for job  device_add_snmpcollector  (ID 160)  Error 404"

But the job has been correctly triggered

image

There is any workarround I can do to get the build related info ( status/url/etc) ?

Contributor guide

Research direction
Inspect the `GetBuild` method in the gojenkins library to understand how it constructs the API request. Trace the flow from `InvokeSimple` to `GetBuild` to see if the job build number is correctly retrieved or if there is a timing issue. Check the Jenkins API endpoint for retrieving builds after job invocation.
Tech stack
go
Domain
api
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75