On 07/21/2015 04:05 PM, Abhishek Shrivastava wrote:
If you want to create a new job then refer "*dsvm-cinder-driver.yaml.sample*", and regarding "*noop-check-communication*" its just for testing the first time don't modify it.


Well, I understand. But I don't think this little change will cause a problem.

I think, if noop-check-communication was executed, the file should be created under /tmp.

I just asked the  same question in IRC meeting, but not resolved yet.

Thanks. :)

On Tue, Jul 21, 2015 at 1:19 PM, Tang Chen <[email protected] <mailto:[email protected]>> wrote:


    On 07/21/2015 03:35 PM, Abhishek Shrivastava wrote:
    Hi Tang,

    Can you please send me the whole job snippet you wrote.

    In /etc/jenkins_jobs/config/ examples.yaml, that's all.

    - job-template:
        name: 'noop-check-communication'
        node: '{node}'

        builders:
          - shell: |
              #!/bin/bash -xe
              touch /tmp/noop-check-communication
              echo "Hello world, this is the {vendor} Testing System"
          - link-logs  # In macros.yaml from os-ext-testing

    #    publishers:
    #      - devstack-logs  # In macros.yaml from os-ext-testing
    #      - console-log  # In macros.yaml from os-ext-testing



    noop-check-communication was setup by default. I didn't change
    anything else.


    BTW, I tried to ask this in #openstack-meeting IRC.
    But no one seems to be active. :)

    Thanks.



    On Tue, Jul 21, 2015 at 12:52 PM, Tang Chen
    <[email protected] <mailto:[email protected]>> wrote:

        Hi Asselin, Abhishek,

        I got some problems when I was trying to write a jenkins job.

        I found that when zuul received the notification from gerrit,
        jenkins didn't run the test.

        I added something to noop-check-communication in
        /etc/jenkins_jobs/config/ examples.yaml,
        just touched a file under /tmp.

        - job-template:
            name: 'noop-check-communication'
            node: '{node}'

            builders:
              - shell: |
                  #!/bin/bash -xe
                  touch /tmp/noop-check-communication # I added
        something here.
                  echo "Hello world, this is the {vendor} Testing System"
              - link-logs  # In macros.yaml from os-ext-testing

        And I flushed the jobs, using jenkins-jobs --flush-cache
        update /etc/jenkins_jobs/config/.
        I can build the job in jenkins web UI, and the file was touched.


        But when I send a patch, the file was not touched. But CI
        really works.
        I can see it on the web site. (
        https://review.openstack.org/#/c/203941/)

        How do you think of this ?




        
__________________________________________________________________________
        OpenStack Development Mailing List (not for usage questions)
        Unsubscribe:
        [email protected]?subject:unsubscribe
        <http://[email protected]?subject:unsubscribe>
        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




-- *
    *
    *Thanks & Regards,
    *
    *Abhishek*
    /_Cloudbyte Inc. <http://www.cloudbyte.com>_/


    __________________________________________________________________________
    OpenStack Development Mailing List (not for usage questions)
    Unsubscribe:[email protected]?subject:unsubscribe  
<mailto:[email protected]?subject:unsubscribe>
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


    __________________________________________________________________________
    OpenStack Development Mailing List (not for usage questions)
    Unsubscribe:
    [email protected]?subject:unsubscribe
    <http://[email protected]?subject:unsubscribe>
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
*
*
*Thanks & Regards,
*
*Abhishek*
/_Cloudbyte Inc. <http://www.cloudbyte.com>_/


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to