Date   
Upcoming Event: EdgeX TSC DevOps WG Meeting (Weekly) - Thu, 01/16/2020 9:00am-10:00am, Please RSVP #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder: EdgeX TSC DevOps WG Meeting (Weekly)

When: Thursday, 16 January 2020, 9:00am to 10:00am, (GMT-08:00) America/Los Angeles

Where:https://zoom.us/j/967227826

An RSVP is requested. Click here to RSVP

Organizer: EdgeX-TSC-DevOps@...

Description: EdgeX TSC DevOps and QA/Test WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

Upcoming Event: EdgeX TSC DevOps WG Meeting (Weekly) - Thu, 01/09/2020 9:00am-10:00am, Please RSVP #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder: EdgeX TSC DevOps WG Meeting (Weekly)

When: Thursday, 9 January 2020, 9:00am to 10:00am, (GMT-08:00) America/Los Angeles

Where:https://zoom.us/j/967227826

An RSVP is requested. Click here to RSVP

Organizer: EdgeX-TSC-DevOps@...

Description: EdgeX TSC DevOps and QA/Test WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

Upcoming Event: EdgeX TSC DevOps WG Meeting (Weekly) - Thu, 12/19/2019 9:00am-10:00am, Please RSVP #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder: EdgeX TSC DevOps WG Meeting (Weekly)

When: Thursday, 19 December 2019, 9:00am to 10:00am, (GMT-08:00) America/Los Angeles

Where:https://zoom.us/j/967227826

An RSVP is requested. Click here to RSVP

Organizer: EdgeX-TSC-DevOps@...

Description: EdgeX TSC DevOps WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

Upcoming Event: EdgeX TSC DevOps WG Meeting (Weekly) - Thu, 12/12/2019 9:00am-10:00am, Please RSVP #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder: EdgeX TSC DevOps WG Meeting (Weekly)

When: Thursday, 12 December 2019, 9:00am to 10:00am, (GMT-08:00) America/Los Angeles

Where:https://zoom.us/j/967227826

An RSVP is requested. Click here to RSVP

Organizer: EdgeX-TSC-DevOps@...

Description: EdgeX TSC DevOps WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

Cancelled Event: EdgeX TSC DevOps WG Meeting (Weekly) - Thursday, 5 December 2019 #cal-cancelled

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Cancelled: EdgeX TSC DevOps WG Meeting (Weekly)

This event has been cancelled.

When:
Thursday, 5 December 2019
9:00am to 10:00am
(UTC-08:00) America/Los Angeles

Where:
https://zoom.us/j/967227826

Organizer: EdgeX-TSC-DevOps@...

Description:
EdgeX TSC DevOps WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

Re: [Edgex-tsc-device-services] Swagger API document development process

Gregg, James R
 

Thank you Cloud. Sounds like a good plan and appreciate the heads up. 


On Nov 27, 2019, at 5:56 PM, Cloud Tsai <cloud@...> wrote:


Hi James,

Yes, we will open an issue, and this mail is just a heads up.
Once we confirm the approach, I will write down more information for explanation, but DevOps meeting is too late to me (1:00 AM).
We will open the issue and even the PR, and we just need your team to review.  Basically, once we switch RAML to Swagger, we need to modify the API document generation job.  I assume it happens automatically now.

On Thu, 28 Nov 2019 at 08:48, Gregg, James R <james.r.gregg@...> wrote:
Cloud, 
Would you like to write up the help needed and submit an issue to ci-management rep?   That way DevOps can assess the work involved.  I’m not clear what help is needed  from DevOps per this email.  We may want to ask you or a rep to come into the next DevOps WG meeting. 
Our scope for Geneva is set for the Jenkins Pipeline transformation, but if we have bandwidth and this is a priority that enables the project we can try to pull in this additional scope. 

Thanks. 

James Gregg

Thank you. 


On Nov 27, 2019, at 3:49 PM, Cloud Tsai <cloud@...> wrote:


Hi all,

As promised last week, we have found out some alternative ways to generate API documents from the swagger files on GitHub.
If you didn't join the QA Working Group meeting this week, you can listen to the recording in 11:17 ~ 18:28.  My colleague, Andrew Foster, explained the ways we found out.
https://zoom.us/recording/share/sXM4tUWvQUKLoO2DTlr3Z_NNDJoocXgBmRXlaOyKrUawIumekTziMw

Due to the limitation, we can't sync swagger file from GitHub to SwaggerHub or vice versa.  SwaggerHub misses the signoff feature to commit changes, so it will never pass our DCO.

There is a command line tool called swagger-codegen, and it can generate html from swagger (core-command sample attached) as what we did using raml2html currently.  We can leverage it to generate HTML file on Jenkins and push to our document website.  Here is our current API page with RAML:

However, we just found another better way.   There is an online API on SwaggerHub, and we verify it works fine.  Please see the attached slide we summarized, and the API sample is on page 3.  After PR merged, we can push the swagger file to SwaggerHub automatically via Jenkins jobs instead of generate HTML and put the SwaggerHub document link on our document web site, like this:
We need DevOps team's support on this part.

As a result, the process will be:
  1. Use any of your favorite swagger editor, such as https://editor.swagger.io/ to create or modify the API definition.  Note that we should all use the latest version openapi: 3.0.1, not swagger 2.0.
  2. Commit the file onto GitHub.
  3. GitHub PR merge trigger the Jenkins job.
  4. The Jenkins job determines whether the API documents are modified, if yes, post to SwaggerHub API according to the version.
Please let me know if you have any question or advice.  Thanks.

--
Best Regards,
Cloud Tsai
<Swagger update.pdf>
<core-command.zip>


--
Best Regards,
Cloud Tsai

Re: [Edgex-tsc-device-services] Swagger API document development process

Cloud Tsai
 

Hi James,

Yes, we will open an issue, and this mail is just a heads up.
Once we confirm the approach, I will write down more information for explanation, but DevOps meeting is too late to me (1:00 AM).
We will open the issue and even the PR, and we just need your team to review.  Basically, once we switch RAML to Swagger, we need to modify the API document generation job.  I assume it happens automatically now.

On Thu, 28 Nov 2019 at 08:48, Gregg, James R <james.r.gregg@...> wrote:
Cloud, 
Would you like to write up the help needed and submit an issue to ci-management rep?   That way DevOps can assess the work involved.  I’m not clear what help is needed  from DevOps per this email.  We may want to ask you or a rep to come into the next DevOps WG meeting. 
Our scope for Geneva is set for the Jenkins Pipeline transformation, but if we have bandwidth and this is a priority that enables the project we can try to pull in this additional scope. 

Thanks. 

James Gregg

Thank you. 


On Nov 27, 2019, at 3:49 PM, Cloud Tsai <cloud@...> wrote:


Hi all,

As promised last week, we have found out some alternative ways to generate API documents from the swagger files on GitHub.
If you didn't join the QA Working Group meeting this week, you can listen to the recording in 11:17 ~ 18:28.  My colleague, Andrew Foster, explained the ways we found out.
https://zoom.us/recording/share/sXM4tUWvQUKLoO2DTlr3Z_NNDJoocXgBmRXlaOyKrUawIumekTziMw

Due to the limitation, we can't sync swagger file from GitHub to SwaggerHub or vice versa.  SwaggerHub misses the signoff feature to commit changes, so it will never pass our DCO.

There is a command line tool called swagger-codegen, and it can generate html from swagger (core-command sample attached) as what we did using raml2html currently.  We can leverage it to generate HTML file on Jenkins and push to our document website.  Here is our current API page with RAML:

However, we just found another better way.   There is an online API on SwaggerHub, and we verify it works fine.  Please see the attached slide we summarized, and the API sample is on page 3.  After PR merged, we can push the swagger file to SwaggerHub automatically via Jenkins jobs instead of generate HTML and put the SwaggerHub document link on our document web site, like this:
We need DevOps team's support on this part.

As a result, the process will be:
  1. Use any of your favorite swagger editor, such as https://editor.swagger.io/ to create or modify the API definition.  Note that we should all use the latest version openapi: 3.0.1, not swagger 2.0.
  2. Commit the file onto GitHub.
  3. GitHub PR merge trigger the Jenkins job.
  4. The Jenkins job determines whether the API documents are modified, if yes, post to SwaggerHub API according to the version.
Please let me know if you have any question or advice.  Thanks.

--
Best Regards,
Cloud Tsai
<Swagger update.pdf>
<core-command.zip>


--
Best Regards,
Cloud Tsai

Re: [Edgex-tsc-device-services] Swagger API document development process

Gregg, James R
 

Cloud, 
Would you like to write up the help needed and submit an issue to ci-management rep?   That way DevOps can assess the work involved.  I’m not clear what help is needed  from DevOps per this email.  We may want to ask you or a rep to come into the next DevOps WG meeting. 
Our scope for Geneva is set for the Jenkins Pipeline transformation, but if we have bandwidth and this is a priority that enables the project we can try to pull in this additional scope. 

Thanks. 

James Gregg

Thank you. 


On Nov 27, 2019, at 3:49 PM, Cloud Tsai <cloud@...> wrote:


Hi all,

As promised last week, we have found out some alternative ways to generate API documents from the swagger files on GitHub.
If you didn't join the QA Working Group meeting this week, you can listen to the recording in 11:17 ~ 18:28.  My colleague, Andrew Foster, explained the ways we found out.
https://zoom.us/recording/share/sXM4tUWvQUKLoO2DTlr3Z_NNDJoocXgBmRXlaOyKrUawIumekTziMw

Due to the limitation, we can't sync swagger file from GitHub to SwaggerHub or vice versa.  SwaggerHub misses the signoff feature to commit changes, so it will never pass our DCO.

There is a command line tool called swagger-codegen, and it can generate html from swagger (core-command sample attached) as what we did using raml2html currently.  We can leverage it to generate HTML file on Jenkins and push to our document website.  Here is our current API page with RAML:

However, we just found another better way.   There is an online API on SwaggerHub, and we verify it works fine.  Please see the attached slide we summarized, and the API sample is on page 3.  After PR merged, we can push the swagger file to SwaggerHub automatically via Jenkins jobs instead of generate HTML and put the SwaggerHub document link on our document web site, like this:
We need DevOps team's support on this part.

As a result, the process will be:
  1. Use any of your favorite swagger editor, such as https://editor.swagger.io/ to create or modify the API definition.  Note that we should all use the latest version openapi: 3.0.1, not swagger 2.0.
  2. Commit the file onto GitHub.
  3. GitHub PR merge trigger the Jenkins job.
  4. The Jenkins job determines whether the API documents are modified, if yes, post to SwaggerHub API according to the version.
Please let me know if you have any question or advice.  Thanks.

--
Best Regards,
Cloud Tsai
<Swagger update.pdf>
<core-command.zip>

Swagger API document development process

Cloud Tsai
 

Hi all,

As promised last week, we have found out some alternative ways to generate API documents from the swagger files on GitHub.
If you didn't join the QA Working Group meeting this week, you can listen to the recording in 11:17 ~ 18:28.  My colleague, Andrew Foster, explained the ways we found out.
https://zoom.us/recording/share/sXM4tUWvQUKLoO2DTlr3Z_NNDJoocXgBmRXlaOyKrUawIumekTziMw

Due to the limitation, we can't sync swagger file from GitHub to SwaggerHub or vice versa.  SwaggerHub misses the signoff feature to commit changes, so it will never pass our DCO.

There is a command line tool called swagger-codegen, and it can generate html from swagger (core-command sample attached) as what we did using raml2html currently.  We can leverage it to generate HTML file on Jenkins and push to our document website.  Here is our current API page with RAML:

However, we just found another better way.   There is an online API on SwaggerHub, and we verify it works fine.  Please see the attached slide we summarized, and the API sample is on page 3.  After PR merged, we can push the swagger file to SwaggerHub automatically via Jenkins jobs instead of generate HTML and put the SwaggerHub document link on our document web site, like this:
We need DevOps team's support on this part.

As a result, the process will be:
  1. Use any of your favorite swagger editor, such as https://editor.swagger.io/ to create or modify the API definition.  Note that we should all use the latest version openapi: 3.0.1, not swagger 2.0.
  2. Commit the file onto GitHub.
  3. GitHub PR merge trigger the Jenkins job.
  4. The Jenkins job determines whether the API documents are modified, if yes, post to SwaggerHub API according to the version.
Please let me know if you have any question or advice.  Thanks.

--
Best Regards,
Cloud Tsai

Cancelled Event: EdgeX TSC DevOps WG Meeting (Weekly) - Thursday, 28 November 2019 #cal-cancelled

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Cancelled: EdgeX TSC DevOps WG Meeting (Weekly)

This event has been cancelled.

When:
Thursday, 28 November 2019
9:00am to 10:00am
(UTC-08:00) America/Los Angeles

Where:
https://zoom.us/j/967227826

Organizer: EdgeX-TSC-DevOps@...

Description:
EdgeX TSC DevOps WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

Upcoming Event: EdgeX TSC DevOps WG Meeting (Weekly) - Thu, 11/21/2019 9:00am-10:00am, Please RSVP #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder: EdgeX TSC DevOps WG Meeting (Weekly)

When: Thursday, 21 November 2019, 9:00am to 10:00am, (GMT-08:00) America/Los Angeles

Where:https://zoom.us/j/967227826

An RSVP is requested. Click here to RSVP

Organizer: EdgeX-TSC-DevOps@...

Description: EdgeX TSC DevOps WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

Re: [Edgex-tsc] Scheduled maintenance: nexus3.edgexfoundry.org, 2019-11-19 17:00-18:00 PST

Gregg, James R
 

Thank you Eric. 
As a topic for DevOps WG this week we would like to understand more about how we’ll take advantage of the new capabilities that are offered in this upgrade. Specifically the Go Module caching capability and any changes needed for its use. 
Ernesto will chair the meeting this week as I have a conflict. 

Thanks again. 

James Gregg 


On Nov 19, 2019, at 6:49 PM, Eric Ball <eball@...> wrote:


This work is now complete. Nexus has been upgraded, and seems to be working fine. I'll keep an eye on jobs currently running to see that all pushes and pulls work as expected.

On Tue, Nov 19, 2019 at 12:10 PM Jim White <jim@...> wrote:
great - thanks Eric.  I know James was looking forward to this upgrade.
Jim White
CTO, IOTech
EdgeX Foundry co-founder
On EdgeX Slack @ jpwhite
612-916-6693


On Tue, 19 Nov 2019 at 13:00, Eric Ball <eball@...> wrote:
What:
Nexus 3 is being upgraded to 3.19.1. Jenkins jobs will need to be suspended while this is completed.

When:
Tuesday 2019-11-19 17:00-18:00 PST

Impact:
Jenkins jobs will be suspended, and Nexus 3 will be temporarily unavailable.

Why:
We need to update from 3.15 to at least 3.17 to enable Go proxying. Nexus has issued a security advisory for all versions prior to 3.19.1, so we are just going all the way to the latest version.

Re: [Edgex-tsc] Scheduled maintenance: nexus3.edgexfoundry.org, 2019-11-19 17:00-18:00 PST

Eric Ball
 

This work is now complete. Nexus has been upgraded, and seems to be working fine. I'll keep an eye on jobs currently running to see that all pushes and pulls work as expected.


On Tue, Nov 19, 2019 at 12:10 PM Jim White <jim@...> wrote:
great - thanks Eric.  I know James was looking forward to this upgrade.
Jim White
CTO, IOTech
EdgeX Foundry co-founder
On EdgeX Slack @ jpwhite
612-916-6693


On Tue, 19 Nov 2019 at 13:00, Eric Ball <eball@...> wrote:
What:
Nexus 3 is being upgraded to 3.19.1. Jenkins jobs will need to be suspended while this is completed.

When:
Tuesday 2019-11-19 17:00-18:00 PST

Impact:
Jenkins jobs will be suspended, and Nexus 3 will be temporarily unavailable.

Why:
We need to update from 3.15 to at least 3.17 to enable Go proxying. Nexus has issued a security advisory for all versions prior to 3.19.1, so we are just going all the way to the latest version.

Re: [Edgex-tsc] Scheduled maintenance: nexus3.edgexfoundry.org, 2019-11-19 17:00-18:00 PST

Jim White
 

great - thanks Eric.  I know James was looking forward to this upgrade.
Jim White
CTO, IOTech
EdgeX Foundry co-founder
On EdgeX Slack @ jpwhite
612-916-6693


On Tue, 19 Nov 2019 at 13:00, Eric Ball <eball@...> wrote:
What:
Nexus 3 is being upgraded to 3.19.1. Jenkins jobs will need to be suspended while this is completed.

When:
Tuesday 2019-11-19 17:00-18:00 PST

Impact:
Jenkins jobs will be suspended, and Nexus 3 will be temporarily unavailable.

Why:
We need to update from 3.15 to at least 3.17 to enable Go proxying. Nexus has issued a security advisory for all versions prior to 3.19.1, so we are just going all the way to the latest version.

Scheduled maintenance: nexus3.edgexfoundry.org, 2019-11-19 17:00-18:00 PST

Eric Ball
 

What:
Nexus 3 is being upgraded to 3.19.1. Jenkins jobs will need to be suspended while this is completed.

When:
Tuesday 2019-11-19 17:00-18:00 PST

Impact:
Jenkins jobs will be suspended, and Nexus 3 will be temporarily unavailable.

Why:
We need to update from 3.15 to at least 3.17 to enable Go proxying. Nexus has issued a security advisory for all versions prior to 3.19.1, so we are just going all the way to the latest version.

Upcoming Event: EdgeX TSC DevOps WG Meeting (Weekly) - Thu, 11/14/2019 9:00am-10:00am, Please RSVP #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder: EdgeX TSC DevOps WG Meeting (Weekly)

When: Thursday, 14 November 2019, 9:00am to 10:00am, (GMT-08:00) America/Los Angeles

Where:https://zoom.us/j/967227826

An RSVP is requested. Click here to RSVP

Organizer: EdgeX-TSC-DevOps@...

Description: EdgeX TSC DevOps WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

EdgeX Fuji Release Date pushed to Friday - November 15, 2019

Rashidi-ranjbar, Lisa A
 

Hi Everyone,

 

We are now targeting 11:59PM UTC November 13, 2019 to get any bug fixes in for the Fuji release.

 

During the EdgeX F2F there were several issues found, triaged and fixed. I want to thank everyone who went above and beyond during the F2F!

 

As a result the Security WG has requested extra time to do some manual testing and will send out a report by email on Tuesday November 12, 2019.

 

Thanks,

Lisa Ranjbar

EdgeX Foundry Release Tsar

Cancelled Event: EdgeX TSC DevOps WG Meeting (Weekly) - Thursday, 7 November 2019 #cal-cancelled

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Cancelled: EdgeX TSC DevOps WG Meeting (Weekly)

This event has been cancelled.

When:
Thursday, 7 November 2019
9:00am to 10:00am
(UTC-08:00) America/Los Angeles

Where:
https://zoom.us/j/967227826

Organizer: EdgeX-TSC-DevOps@...

Description:
EdgeX TSC DevOps WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

Upcoming Event: EdgeX TSC DevOps WG Meeting (Weekly) - Thu, 10/31/2019 9:00am-10:00am, Please RSVP #cal-reminder

EdgeX-TSC-DevOps@lists.edgexfoundry.org Calendar <EdgeX-TSC-DevOps@...>
 

Reminder: EdgeX TSC DevOps WG Meeting (Weekly)

When: Thursday, 31 October 2019, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/967227826

An RSVP is requested. Click here to RSVP

Organizer: EdgeX-TSC-DevOps@...

Description: EdgeX TSC DevOps WG Meeting. Meeting content posted to DevOps Wiki.
Meeting Lead: James Gregg, EdgeX DevOps WG Chair, james.r.gregg@...
-----
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/967227826

Or iPhone one-tap :
    US: +16465588656,,967227826# or +16699006833,,967227826# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 967 227 826
    International numbers available: https://zoom.us/u/bmaYSxofb

Re: Branches Cut for Fuji

Cloud Tsai
 

Hi DevOps team,

Please also help create a tag to fuji branch in device-sdk-go as "v1.1.0", and we will update the go.mod in each Go Device Services to use this tag.
Thanks.

On Sat, 26 Oct 2019 at 08:17, Jim White <jim@...> wrote:
Great work Lisa and team. Again,  thanks to everyone that is working to make this release happen. 


On Fri, Oct 25, 2019, 8:14 PM Rashidi-ranjbar, Lisa A <lisa.a.rashidi-ranjbar@...> wrote:

Hi All,

 

This is to inform the community we have cut the branches for Fuji in the repos that require branches today. (Thanks Ernesto)

 

Moving forward bug fixes will need to go into both master and fuji branches.

 

All bug fixes for Fuji need to be merged in by November 10, 2019 11:59PM UTC.

 

DevOps will now start creating jobs and making CI-related updates in the repos.

 

We are all working towards a release date of November 13, 2019.

 

Thanks,

Lisa Ranjbar

Release Tsar



--
Best Regards,
Cloud Tsai