public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Claudius Heine <claudius.heine.ext@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Jenkins project configuration by user
Date: Thu, 30 May 2019 10:29:25 +0200	[thread overview]
Message-ID: <d9bfa222-539e-0c6e-83af-87a81e03ed03@ilbers.de> (raw)
In-Reply-To: <b5c9fb55-5d59-8be4-ccdd-d6fd45edda76@siemens.com>

Hi isar-build.org users,

On 5/22/19 9:26 AM, Claudius Heine wrote:
<snip>
>   - Not transparent configuration/environment:
>     -> parameters with which ci_build.sh is called are not controllable 
> from the repository

To address this issue I've added the ability to user to configure his 
project - just click button 'Configure' on the left pane of your project
http://isar-build.org:8080/job/<your_project_name>/configure

Here you can change parameters passed to ci_build, tweak build triggers etc.

If you want to initiate the build on push request to your repository

1) Add a webhook in your github isar repository:


Payload URL:
http://ci.isar-build.org:8080/github-webhook/

Content type:
application/json

Secret:
<empty>

Radio-button:
Just the push event

Tick as active.

2) Enable option 'GitHub hook trigger for GITScm polling" in the section 
Build Triggers of project's configuration.

Regards,
Maxim.

-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov

      parent reply	other threads:[~2019-05-30  8:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22  7:26 [DISCUSSIONS] CI build Claudius Heine
2019-05-22  8:20 ` Maxim Yu. Osipov
2019-05-22  9:10   ` Claudius Heine
2019-05-22  9:50     ` Maxim Yu. Osipov
2019-05-22 11:28       ` Claudius Heine
2019-05-23  8:10         ` Claudius Heine
2019-05-23 13:43           ` Claudius Heine
2019-05-23 13:56             ` Maxim Yu. Osipov
2019-05-23 14:36               ` Claudius Heine
2019-05-22 19:44 ` Baurzhan Ismagulov
2019-05-23  4:44   ` Jan Kiszka
2019-05-23  8:32     ` Claudius Heine
2019-05-23  8:39       ` Jan Kiszka
2019-05-23 10:58       ` Maxim Yu. Osipov
2019-05-23 11:35 ` Henning Schild
2019-05-23 12:11   ` Baurzhan Ismagulov
2019-05-30  8:29 ` Maxim Yu. Osipov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d9bfa222-539e-0c6e-83af-87a81e03ed03@ilbers.de \
    --to=mosipov@ilbers.de \
    --cc=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox