[JIRA] (JENKINS-42178) pipeline as code/multi branch pipeline jobs events

1 view
Skip to first unread message

grose.matthewf@gmail.com (JIRA)

unread,
Feb 19, 2017, 11:30:01 AM2/19/17
to jenkinsc...@googlegroups.com
mg created an issue
 
Jenkins / New Feature JENKINS-42178
pipeline as code/multi branch pipeline jobs events
Issue Type: New Feature New Feature
Assignee: Ted
Components: splunk-devops-plugin
Created: 2017/Feb/19 4:29 PM
Priority: Minor Minor
Reporter: mg

What is the built in support for pipeline as code/multi branch pipeline jobs and tracking events from within that context (stages, etc)?

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

xiao.xj@outlook.com (JIRA)

unread,
Feb 19, 2017, 10:23:01 PM2/19/17
to jenkinsc...@googlegroups.com
Ted commented on New Feature JENKINS-42178
 
Re: pipeline as code/multi branch pipeline jobs events

pipeline support is provided by a separate plugin splunk-devops-extend, stage is supported out of box(no additional configure is required), but currently stage information is not showed on the app , you have to get it from jenkins_statistics index

Sample

index=jenkins_statistics event_tag=job_event job_name=* stages

{
    "build_number": 2,
    "build_url": "job/blah/2/",
    "event_tag": "job_event",
    "job_duration": 2123.701,
    "job_name": "job/blah/",
    "job_result": "SUCCESS",
    "job_started_at": "2017-02-17T18:55:02Z",
    "job_type": "Pipeline",
    "label": "master",
    "node": "(master)",
    "queue_id": 7059,
    "queue_time": 0.069,
    "scm": "git",
    "stages": [
        {
            "duration": 47.503,
            "id": "23",
            "name": "Clone Repo",
            "pause_duration": 0.0,
            "start_time": 1487358141,
            "status": "SUCCESS"
        },
        {
            "duration": 960.245,
            "id": "115",
            "name": "Static Analysis",
            "pause_duration": 0.0,
            "start_time": 1487358357,
            "status": "SUCCESS"
        },
        {
            "duration": 22.6,
            "id": "273",
            "name": "Negative API tests",
            "pause_duration": 0.0,
            "start_time": 1487359317,
            "status": "SUCCESS"
        }
    ],
    "test_summary": {
        "duration": 0.0,
        "failures": 0,
        "passes": 0,
        "skips": 0,
        "total": 0
    },
    "trigger_by": "Branch indexing",
    "type": "completed",
    "upstream": "",
    "user": "anonymous"
}

grose.matthewf@gmail.com (JIRA)

unread,
Feb 22, 2017, 5:48:01 PM2/22/17
to jenkinsc...@googlegroups.com
mg commented on New Feature JENKINS-42178

Ted very cool, looking forward to digging in. is there any thoughts or recommendations on surfacing deployment tracking with this set up? with minimal hands on usage, first thoughts would be along the lines of utilizing the other pipeline plugin to essentially call a method and "mark" moments in time as deployments with attributes (ie. environment, version, etc) that could be surfaced and visualized in the splunk app?

xiao.xj@outlook.com (JIRA)

unread,
Mar 12, 2020, 6:48:03 AM3/12/20
to jenkinsc...@googlegroups.com
Change By: Ted Xiao
Status: Open Fixed but Unreleased
Resolution: Fixed
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages