github and git repo still behind subversion
Locked
 
|
Hey folks, it seems we still have this delay in our git account. Any
idea how to resolve this and why does it keep happening? |
Re: github and git repo still behind subversion
|
It seems that is not the only service lagging in providing correct results.
The same applies to fisheye. See https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk Best regards, Pierre Smits V.P. Apache Trafodion On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb <[hidden email]> wrote: > Hey folks, it seems we still have this delay in our git account. Any > idea how to resolve this and why does it keep happening? > |
Re: github and git repo still behind subversion
|
|
BTW, do we have documentation somewhere which explains who is
responsible for these services, how they work, where to lokk what's wrong and who to inform if there are issues? To me this is not clear for some of the services (like publishing the website, fisheye, GitHub sync, ...) , but I admit that I did not try very hard to find information about it. Thanks, Michael Am 07.01.18 um 16:29 schrieb Pierre Smits: > It seems that is not the only service lagging in providing correct results. > The same applies to fisheye. See > https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk > > > Best regards, > > Pierre Smits > > V.P. Apache Trafodion > > On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb <[hidden email]> > wrote: > >> Hey folks, it seems we still have this delay in our git account. Any >> idea how to resolve this and why does it keep happening? >> |
smime.p7s (5K)
Re: github and git repo still behind subversion
Administrator
|
So far I simply got to the Infra HipChat room and asked there.
Very successful most of the time, but not documented apart some messages I sent to this ML and bookmarks I kept on them for myself, like "[FYI] Let's encrypt certificate renewal failed" Note that with infra things are moving fast and the documentation, rarely used, can be deprecated in few years or even months. I did not say we should not have ;) Also, for simple things like lagging apps., you can't do much but asking on Infra HipChat room (not ML , they don't like) or even ask for service when you must: https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3 Jacques Le 07/01/2018 à 16:56, Michael Brohl a écrit : > BTW, do we have documentation somewhere which explains who is responsible for these services, how they work, where to lokk what's wrong and who to > inform if there are issues? > > To me this is not clear for some of the services (like publishing the website, fisheye, GitHub sync, ...) , but I admit that I did not try very hard > to find information about it. > > Thanks, > > Michael > > > Am 07.01.18 um 16:29 schrieb Pierre Smits: >> It seems that is not the only service lagging in providing correct results. >> The same applies to fisheye. See >> https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk >> >> >> Best regards, >> >> Pierre Smits >> >> V.P. Apache Trafodion >> >> On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb <[hidden email]> >> wrote: >> >>> Hey folks, it seems we still have this delay in our git account. Any >>> idea how to resolve this and why does it keep happening? >>> > > |
Re: github and git repo still behind subversion
|
|
Similarly to the OFBiz project, INFRA is for the greater part staffed with
volunteers (but I may have outdated insights). More often than not, and due to the inability to enforce volunteers (with commitments beyond the project) to take action on something they do not desire) this leads to a technical debt regarding documentation. Also like our project. Only one volunteer needs to step up to take the action, either to update the documentation at INFRA (beyond our control), or in our confluence to help our volunteers interacting with INFRA. Best regards, Pierre Smits V.P. Apache Trafodion, PMC Member Apache Directory On Sun, Jan 7, 2018 at 5:36 PM, Jacques Le Roux < [hidden email]> wrote: > So far I simply got to the Infra HipChat room and asked there. > > Very successful most of the time, but not documented apart some messages I > sent to this ML and bookmarks I kept on them for myself, like "[FYI] Let's > encrypt certificate renewal failed" > > Note that with infra things are moving fast and the documentation, rarely > used, can be deprecated in few years or even months. I did not say we > should not have ;) > > Also, for simple things like lagging apps., you can't do much but asking > on Infra HipChat room (not ML , they don't like) or even ask for service > when you must: https://issues.apache.org/jira/servicedesk/customer/portal/ > 1/create/3 > > Jacques > > > > Le 07/01/2018 à 16:56, Michael Brohl a écrit : > >> BTW, do we have documentation somewhere which explains who is responsible >> for these services, how they work, where to lokk what's wrong and who to >> inform if there are issues? >> >> To me this is not clear for some of the services (like publishing the >> website, fisheye, GitHub sync, ...) , but I admit that I did not try very >> hard to find information about it. >> >> Thanks, >> >> Michael >> >> >> Am 07.01.18 um 16:29 schrieb Pierre Smits: >> >>> It seems that is not the only service lagging in providing correct >>> results. >>> The same applies to fisheye. See >>> https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk >>> >>> >>> Best regards, >>> >>> Pierre Smits >>> >>> V.P. Apache Trafodion >>> >>> On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb < >>> [hidden email]> >>> wrote: >>> >>> Hey folks, it seems we still have this delay in our git account. Any >>>> idea how to resolve this and why does it keep happening? >>>> >>>> >> >> > |
|
|
If anyone has information to share that would be great, or at least as
Michael pointed out if you know any documentation anywhere that can help us identify how mirroring is done so we can resolve the issue ourselves in the future then we can resolve this more quickly. Perhaps we should start a new JIRA with infra but I'm not sure. Is that appropriate or do we have a pending JIRA already? On Sun, Jan 7, 2018 at 9:17 PM, Pierre Smits <[hidden email]> wrote: > Similarly to the OFBiz project, INFRA is for the greater part staffed with > volunteers (but I may have outdated insights). More often than not, and due > to the inability to enforce volunteers (with commitments beyond the > project) to take action on something they do not desire) this leads to a > technical debt regarding documentation. Also like our project. > > Only one volunteer needs to step up to take the action, either to update > the documentation at INFRA (beyond our control), or in our confluence to > help our volunteers interacting with INFRA. > > Best regards, > > Pierre Smits > > V.P. Apache Trafodion, > PMC Member Apache Directory > > On Sun, Jan 7, 2018 at 5:36 PM, Jacques Le Roux < > [hidden email]> wrote: > >> So far I simply got to the Infra HipChat room and asked there. >> >> Very successful most of the time, but not documented apart some messages I >> sent to this ML and bookmarks I kept on them for myself, like "[FYI] Let's >> encrypt certificate renewal failed" >> >> Note that with infra things are moving fast and the documentation, rarely >> used, can be deprecated in few years or even months. I did not say we >> should not have ;) >> >> Also, for simple things like lagging apps., you can't do much but asking >> on Infra HipChat room (not ML , they don't like) or even ask for service >> when you must: https://issues.apache.org/jira/servicedesk/customer/portal/ >> 1/create/3 >> >> Jacques >> >> >> >> Le 07/01/2018 à 16:56, Michael Brohl a écrit : >> >>> BTW, do we have documentation somewhere which explains who is responsible >>> for these services, how they work, where to lokk what's wrong and who to >>> inform if there are issues? >>> >>> To me this is not clear for some of the services (like publishing the >>> website, fisheye, GitHub sync, ...) , but I admit that I did not try very >>> hard to find information about it. >>> >>> Thanks, >>> >>> Michael >>> >>> >>> Am 07.01.18 um 16:29 schrieb Pierre Smits: >>> >>>> It seems that is not the only service lagging in providing correct >>>> results. >>>> The same applies to fisheye. See >>>> https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk >>>> >>>> >>>> Best regards, >>>> >>>> Pierre Smits >>>> >>>> V.P. Apache Trafodion >>>> >>>> On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb < >>>> [hidden email]> >>>> wrote: >>>> >>>> Hey folks, it seems we still have this delay in our git account. Any >>>>> idea how to resolve this and why does it keep happening? >>>>> >>>>> >>> >>> >> |
Re: github and git repo still behind subversion
|
Administrator
|
AFAIK, we don't have a Jira about that.
For Infra issues, we are requested to pass by https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3 or for quick things Hipchat room. Maybe though for such a long term request (documentation) the infra ML can be used (but I think Jira is easier for both side) I fear it could eventually be a karma issue (not enough rights, only infra have) but we can't know w/o asking and karmas can evolve at the ASF... Jacques Le 07/01/2018 à 21:11, Taher Alkhateeb a écrit : > If anyone has information to share that would be great, or at least as > Michael pointed out if you know any documentation anywhere that can > help us identify how mirroring is done so we can resolve the issue > ourselves in the future then we can resolve this more quickly. > > Perhaps we should start a new JIRA with infra but I'm not sure. Is > that appropriate or do we have a pending JIRA already? > > On Sun, Jan 7, 2018 at 9:17 PM, Pierre Smits <[hidden email]> wrote: >> Similarly to the OFBiz project, INFRA is for the greater part staffed with >> volunteers (but I may have outdated insights). More often than not, and due >> to the inability to enforce volunteers (with commitments beyond the >> project) to take action on something they do not desire) this leads to a >> technical debt regarding documentation. Also like our project. >> >> Only one volunteer needs to step up to take the action, either to update >> the documentation at INFRA (beyond our control), or in our confluence to >> help our volunteers interacting with INFRA. >> >> Best regards, >> >> Pierre Smits >> >> V.P. Apache Trafodion, >> PMC Member Apache Directory >> >> On Sun, Jan 7, 2018 at 5:36 PM, Jacques Le Roux < >> [hidden email]> wrote: >> >>> So far I simply got to the Infra HipChat room and asked there. >>> >>> Very successful most of the time, but not documented apart some messages I >>> sent to this ML and bookmarks I kept on them for myself, like "[FYI] Let's >>> encrypt certificate renewal failed" >>> >>> Note that with infra things are moving fast and the documentation, rarely >>> used, can be deprecated in few years or even months. I did not say we >>> should not have ;) >>> >>> Also, for simple things like lagging apps., you can't do much but asking >>> on Infra HipChat room (not ML , they don't like) or even ask for service >>> when you must: https://issues.apache.org/jira/servicedesk/customer/portal/ >>> 1/create/3 >>> >>> Jacques >>> >>> >>> >>> Le 07/01/2018 à 16:56, Michael Brohl a écrit : >>> >>>> BTW, do we have documentation somewhere which explains who is responsible >>>> for these services, how they work, where to lokk what's wrong and who to >>>> inform if there are issues? >>>> >>>> To me this is not clear for some of the services (like publishing the >>>> website, fisheye, GitHub sync, ...) , but I admit that I did not try very >>>> hard to find information about it. >>>> >>>> Thanks, >>>> >>>> Michael >>>> >>>> >>>> Am 07.01.18 um 16:29 schrieb Pierre Smits: >>>> >>>>> It seems that is not the only service lagging in providing correct >>>>> results. >>>>> The same applies to fisheye. See >>>>> https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk >>>>> >>>>> >>>>> Best regards, >>>>> >>>>> Pierre Smits >>>>> >>>>> V.P. Apache Trafodion >>>>> >>>>> On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb < >>>>> [hidden email]> >>>>> wrote: >>>>> >>>>> Hey folks, it seems we still have this delay in our git account. Any >>>>>> idea how to resolve this and why does it keep happening? >>>>>> >>>>>> >>>> |
Re: github and git repo still behind subversion
|
|
Its already reported
https://f.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-15686 Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com www.hotwax.co On Mon, Jan 8, 2018 at 4:08 AM, Jacques Le Roux < [hidden email]> wrote: > AFAIK, we don't have a Jira about that. > > For Infra issues, we are requested to pass by > https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3 or > for quick things Hipchat room. > > Maybe though for such a long term request (documentation) the infra ML can > be used (but I think Jira is easier for both side) > > I fear it could eventually be a karma issue (not enough rights, only infra > have) but we can't know w/o asking and karmas can evolve at the ASF... > > Jacques > > > Le 07/01/2018 à 21:11, Taher Alkhateeb a écrit : > >> If anyone has information to share that would be great, or at least as >> Michael pointed out if you know any documentation anywhere that can >> help us identify how mirroring is done so we can resolve the issue >> ourselves in the future then we can resolve this more quickly. >> >> Perhaps we should start a new JIRA with infra but I'm not sure. Is >> that appropriate or do we have a pending JIRA already? >> >> On Sun, Jan 7, 2018 at 9:17 PM, Pierre Smits <[hidden email]> >> wrote: >> >>> Similarly to the OFBiz project, INFRA is for the greater part staffed >>> with >>> volunteers (but I may have outdated insights). More often than not, and >>> due >>> to the inability to enforce volunteers (with commitments beyond the >>> project) to take action on something they do not desire) this leads to a >>> technical debt regarding documentation. Also like our project. >>> >>> Only one volunteer needs to step up to take the action, either to update >>> the documentation at INFRA (beyond our control), or in our confluence to >>> help our volunteers interacting with INFRA. >>> >>> Best regards, >>> >>> Pierre Smits >>> >>> V.P. Apache Trafodion, >>> PMC Member Apache Directory >>> >>> On Sun, Jan 7, 2018 at 5:36 PM, Jacques Le Roux < >>> [hidden email]> wrote: >>> >>> So far I simply got to the Infra HipChat room and asked there. >>>> >>>> Very successful most of the time, but not documented apart some >>>> messages I >>>> sent to this ML and bookmarks I kept on them for myself, like "[FYI] >>>> Let's >>>> encrypt certificate renewal failed" >>>> >>>> Note that with infra things are moving fast and the documentation, >>>> rarely >>>> used, can be deprecated in few years or even months. I did not say we >>>> should not have ;) >>>> >>>> Also, for simple things like lagging apps., you can't do much but asking >>>> on Infra HipChat room (not ML , they don't like) or even ask for service >>>> when you must: https://issues.apache.org/jira >>>> /servicedesk/customer/portal/ >>>> 1/create/3 >>>> >>>> Jacques >>>> >>>> >>>> >>>> Le 07/01/2018 à 16:56, Michael Brohl a écrit : >>>> >>>> BTW, do we have documentation somewhere which explains who is >>>>> responsible >>>>> for these services, how they work, where to lokk what's wrong and who >>>>> to >>>>> inform if there are issues? >>>>> >>>>> To me this is not clear for some of the services (like publishing the >>>>> website, fisheye, GitHub sync, ...) , but I admit that I did not try >>>>> very >>>>> hard to find information about it. >>>>> >>>>> Thanks, >>>>> >>>>> Michael >>>>> >>>>> >>>>> Am 07.01.18 um 16:29 schrieb Pierre Smits: >>>>> >>>>> It seems that is not the only service lagging in providing correct >>>>>> results. >>>>>> The same applies to fisheye. See >>>>>> https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk >>>>>> >>>>>> >>>>>> Best regards, >>>>>> >>>>>> Pierre Smits >>>>>> >>>>>> V.P. Apache Trafodion >>>>>> >>>>>> On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb < >>>>>> [hidden email]> >>>>>> wrote: >>>>>> >>>>>> Hey folks, it seems we still have this delay in our git account. Any >>>>>> >>>>>>> idea how to resolve this and why does it keep happening? >>>>>>> >>>>>>> >>>>>>> >>>>> > |
Re: github and git repo still behind subversion
|
|
Oops here is correct link
https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-15686 http://markmail.org/message/2vy3tprutqe5hqti http://markmail.org/message/ange7ygquw7vc22v Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com www.hotwax.co On Mon, Jan 8, 2018 at 11:42 AM, Deepak Dixit < [hidden email]> wrote: > Its already reported > https://f.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-15686 > > Thanks & Regards > -- > Deepak Dixit > www.hotwaxsystems.com > www.hotwax.co > > On Mon, Jan 8, 2018 at 4:08 AM, Jacques Le Roux < > [hidden email]> wrote: > >> AFAIK, we don't have a Jira about that. >> >> For Infra issues, we are requested to pass by >> https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3 or >> for quick things Hipchat room. >> >> Maybe though for such a long term request (documentation) the infra ML >> can be used (but I think Jira is easier for both side) >> >> I fear it could eventually be a karma issue (not enough rights, only >> infra have) but we can't know w/o asking and karmas can evolve at the ASF... >> >> Jacques >> >> >> Le 07/01/2018 à 21:11, Taher Alkhateeb a écrit : >> >>> If anyone has information to share that would be great, or at least as >>> Michael pointed out if you know any documentation anywhere that can >>> help us identify how mirroring is done so we can resolve the issue >>> ourselves in the future then we can resolve this more quickly. >>> >>> Perhaps we should start a new JIRA with infra but I'm not sure. Is >>> that appropriate or do we have a pending JIRA already? >>> >>> On Sun, Jan 7, 2018 at 9:17 PM, Pierre Smits <[hidden email]> >>> wrote: >>> >>>> Similarly to the OFBiz project, INFRA is for the greater part staffed >>>> with >>>> volunteers (but I may have outdated insights). More often than not, and >>>> due >>>> to the inability to enforce volunteers (with commitments beyond the >>>> project) to take action on something they do not desire) this leads to a >>>> technical debt regarding documentation. Also like our project. >>>> >>>> Only one volunteer needs to step up to take the action, either to update >>>> the documentation at INFRA (beyond our control), or in our confluence to >>>> help our volunteers interacting with INFRA. >>>> >>>> Best regards, >>>> >>>> Pierre Smits >>>> >>>> V.P. Apache Trafodion, >>>> PMC Member Apache Directory >>>> >>>> On Sun, Jan 7, 2018 at 5:36 PM, Jacques Le Roux < >>>> [hidden email]> wrote: >>>> >>>> So far I simply got to the Infra HipChat room and asked there. >>>>> >>>>> Very successful most of the time, but not documented apart some >>>>> messages I >>>>> sent to this ML and bookmarks I kept on them for myself, like "[FYI] >>>>> Let's >>>>> encrypt certificate renewal failed" >>>>> >>>>> Note that with infra things are moving fast and the documentation, >>>>> rarely >>>>> used, can be deprecated in few years or even months. I did not say we >>>>> should not have ;) >>>>> >>>>> Also, for simple things like lagging apps., you can't do much but >>>>> asking >>>>> on Infra HipChat room (not ML , they don't like) or even ask for >>>>> service >>>>> when you must: https://issues.apache.org/jira >>>>> /servicedesk/customer/portal/ >>>>> 1/create/3 >>>>> >>>>> Jacques >>>>> >>>>> >>>>> >>>>> Le 07/01/2018 à 16:56, Michael Brohl a écrit : >>>>> >>>>> BTW, do we have documentation somewhere which explains who is >>>>>> responsible >>>>>> for these services, how they work, where to lokk what's wrong and who >>>>>> to >>>>>> inform if there are issues? >>>>>> >>>>>> To me this is not clear for some of the services (like publishing the >>>>>> website, fisheye, GitHub sync, ...) , but I admit that I did not try >>>>>> very >>>>>> hard to find information about it. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Michael >>>>>> >>>>>> >>>>>> Am 07.01.18 um 16:29 schrieb Pierre Smits: >>>>>> >>>>>> It seems that is not the only service lagging in providing correct >>>>>>> results. >>>>>>> The same applies to fisheye. See >>>>>>> https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk >>>>>>> >>>>>>> >>>>>>> Best regards, >>>>>>> >>>>>>> Pierre Smits >>>>>>> >>>>>>> V.P. Apache Trafodion >>>>>>> >>>>>>> On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb < >>>>>>> [hidden email]> >>>>>>> wrote: >>>>>>> >>>>>>> Hey folks, it seems we still have this delay in our git account. Any >>>>>>> >>>>>>>> idea how to resolve this and why does it keep happening? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>> >> > |
Re: github and git repo still behind subversion
|
|
There are some issue at infra level in pussub service that sync svn with
github. Due to this svn to github auto synching not working. Infra team is looking into it.Here is the issue for pubsub sync https://issues.apache.org/jira/browse/INFRA-15806 Admin team did manual sync and now its updated till recent commit, still new commit will not sync automatically. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com www.hotwax.co On Mon, Jan 8, 2018 at 11:46 AM, Deepak Dixit < [hidden email]> wrote: > Oops here is correct link > https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-15686 > > http://markmail.org/message/2vy3tprutqe5hqti > http://markmail.org/message/ange7ygquw7vc22v > > > Thanks & Regards > -- > Deepak Dixit > www.hotwaxsystems.com > www.hotwax.co > > On Mon, Jan 8, 2018 at 11:42 AM, Deepak Dixit <deepak.dixit@hotwaxsystems. > com> wrote: > >> Its already reported >> https://f.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-15686 >> >> Thanks & Regards >> -- >> Deepak Dixit >> www.hotwaxsystems.com >> www.hotwax.co >> >> On Mon, Jan 8, 2018 at 4:08 AM, Jacques Le Roux < >> [hidden email]> wrote: >> >>> AFAIK, we don't have a Jira about that. >>> >>> For Infra issues, we are requested to pass by >>> https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3 >>> or for quick things Hipchat room. >>> >>> Maybe though for such a long term request (documentation) the infra ML >>> can be used (but I think Jira is easier for both side) >>> >>> I fear it could eventually be a karma issue (not enough rights, only >>> infra have) but we can't know w/o asking and karmas can evolve at the ASF... >>> >>> Jacques >>> >>> >>> Le 07/01/2018 à 21:11, Taher Alkhateeb a écrit : >>> >>>> If anyone has information to share that would be great, or at least as >>>> Michael pointed out if you know any documentation anywhere that can >>>> help us identify how mirroring is done so we can resolve the issue >>>> ourselves in the future then we can resolve this more quickly. >>>> >>>> Perhaps we should start a new JIRA with infra but I'm not sure. Is >>>> that appropriate or do we have a pending JIRA already? >>>> >>>> On Sun, Jan 7, 2018 at 9:17 PM, Pierre Smits <[hidden email]> >>>> wrote: >>>> >>>>> Similarly to the OFBiz project, INFRA is for the greater part staffed >>>>> with >>>>> volunteers (but I may have outdated insights). More often than not, >>>>> and due >>>>> to the inability to enforce volunteers (with commitments beyond the >>>>> project) to take action on something they do not desire) this leads to >>>>> a >>>>> technical debt regarding documentation. Also like our project. >>>>> >>>>> Only one volunteer needs to step up to take the action, either to >>>>> update >>>>> the documentation at INFRA (beyond our control), or in our confluence >>>>> to >>>>> help our volunteers interacting with INFRA. >>>>> >>>>> Best regards, >>>>> >>>>> Pierre Smits >>>>> >>>>> V.P. Apache Trafodion, >>>>> PMC Member Apache Directory >>>>> >>>>> On Sun, Jan 7, 2018 at 5:36 PM, Jacques Le Roux < >>>>> [hidden email]> wrote: >>>>> >>>>> So far I simply got to the Infra HipChat room and asked there. >>>>>> >>>>>> Very successful most of the time, but not documented apart some >>>>>> messages I >>>>>> sent to this ML and bookmarks I kept on them for myself, like "[FYI] >>>>>> Let's >>>>>> encrypt certificate renewal failed" >>>>>> >>>>>> Note that with infra things are moving fast and the documentation, >>>>>> rarely >>>>>> used, can be deprecated in few years or even months. I did not say we >>>>>> should not have ;) >>>>>> >>>>>> Also, for simple things like lagging apps., you can't do much but >>>>>> asking >>>>>> on Infra HipChat room (not ML , they don't like) or even ask for >>>>>> service >>>>>> when you must: https://issues.apache.org/jira >>>>>> /servicedesk/customer/portal/ >>>>>> 1/create/3 >>>>>> >>>>>> Jacques >>>>>> >>>>>> >>>>>> >>>>>> Le 07/01/2018 à 16:56, Michael Brohl a écrit : >>>>>> >>>>>> BTW, do we have documentation somewhere which explains who is >>>>>>> responsible >>>>>>> for these services, how they work, where to lokk what's wrong and >>>>>>> who to >>>>>>> inform if there are issues? >>>>>>> >>>>>>> To me this is not clear for some of the services (like publishing the >>>>>>> website, fisheye, GitHub sync, ...) , but I admit that I did not try >>>>>>> very >>>>>>> hard to find information about it. >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Michael >>>>>>> >>>>>>> >>>>>>> Am 07.01.18 um 16:29 schrieb Pierre Smits: >>>>>>> >>>>>>> It seems that is not the only service lagging in providing correct >>>>>>>> results. >>>>>>>> The same applies to fisheye. See >>>>>>>> https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk >>>>>>>> >>>>>>>> >>>>>>>> Best regards, >>>>>>>> >>>>>>>> Pierre Smits >>>>>>>> >>>>>>>> V.P. Apache Trafodion >>>>>>>> >>>>>>>> On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb < >>>>>>>> [hidden email]> >>>>>>>> wrote: >>>>>>>> >>>>>>>> Hey folks, it seems we still have this delay in our git account. Any >>>>>>>> >>>>>>>>> idea how to resolve this and why does it keep happening? >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> >>> >> > |
|
|
Hi Deepak,
Great! at least the mystery is out. Thank you for the clarification. Can we trigger a manual sync ourselves or is this something affecting all projects and thus only available to infra? I will follow up on that JIRA meanwhile. On Jan 8, 2018 9:38 AM, "Deepak Dixit" <[hidden email]> wrote: > There are some issue at infra level in pussub service that sync svn with > github. Due to this svn to github auto synching not working. > Infra team is looking into it.Here is the issue for pubsub sync > https://issues.apache.org/jira/browse/INFRA-15806 > > Admin team did manual sync and now its updated till recent commit, still > new commit will not sync automatically. > > Thanks & Regards > -- > Deepak Dixit > www.hotwaxsystems.com > www.hotwax.co > > On Mon, Jan 8, 2018 at 11:46 AM, Deepak Dixit < > [hidden email]> wrote: > > > Oops here is correct link > > https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-15686 > > > > http://markmail.org/message/2vy3tprutqe5hqti > > http://markmail.org/message/ange7ygquw7vc22v > > > > > > Thanks & Regards > > -- > > Deepak Dixit > > www.hotwaxsystems.com > > www.hotwax.co > > > > On Mon, Jan 8, 2018 at 11:42 AM, Deepak Dixit > <deepak.dixit@hotwaxsystems. > > com> wrote: > > > >> Its already reported > >> https://f.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-15686 > >> > >> Thanks & Regards > >> -- > >> Deepak Dixit > >> www.hotwaxsystems.com > >> www.hotwax.co > >> > >> On Mon, Jan 8, 2018 at 4:08 AM, Jacques Le Roux < > >> [hidden email]> wrote: > >> > >>> AFAIK, we don't have a Jira about that. > >>> > >>> For Infra issues, we are requested to pass by > >>> https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3 > >>> or for quick things Hipchat room. > >>> > >>> Maybe though for such a long term request (documentation) the infra ML > >>> can be used (but I think Jira is easier for both side) > >>> > >>> I fear it could eventually be a karma issue (not enough rights, only > >>> infra have) but we can't know w/o asking and karmas can evolve at the > ASF... > >>> > >>> Jacques > >>> > >>> > >>> Le 07/01/2018 à 21:11, Taher Alkhateeb a écrit : > >>> > >>>> If anyone has information to share that would be great, or at least as > >>>> Michael pointed out if you know any documentation anywhere that can > >>>> help us identify how mirroring is done so we can resolve the issue > >>>> ourselves in the future then we can resolve this more quickly. > >>>> > >>>> Perhaps we should start a new JIRA with infra but I'm not sure. Is > >>>> that appropriate or do we have a pending JIRA already? > >>>> > >>>> On Sun, Jan 7, 2018 at 9:17 PM, Pierre Smits <[hidden email]> > >>>> wrote: > >>>> > >>>>> Similarly to the OFBiz project, INFRA is for the greater part staffed > >>>>> with > >>>>> volunteers (but I may have outdated insights). More often than not, > >>>>> and due > >>>>> to the inability to enforce volunteers (with commitments beyond the > >>>>> project) to take action on something they do not desire) this leads > to > >>>>> a > >>>>> technical debt regarding documentation. Also like our project. > >>>>> > >>>>> Only one volunteer needs to step up to take the action, either to > >>>>> update > >>>>> the documentation at INFRA (beyond our control), or in our confluence > >>>>> to > >>>>> help our volunteers interacting with INFRA. > >>>>> > >>>>> Best regards, > >>>>> > >>>>> Pierre Smits > >>>>> > >>>>> V.P. Apache Trafodion, > >>>>> PMC Member Apache Directory > >>>>> > >>>>> On Sun, Jan 7, 2018 at 5:36 PM, Jacques Le Roux < > >>>>> [hidden email]> wrote: > >>>>> > >>>>> So far I simply got to the Infra HipChat room and asked there. > >>>>>> > >>>>>> Very successful most of the time, but not documented apart some > >>>>>> messages I > >>>>>> sent to this ML and bookmarks I kept on them for myself, like "[FYI] > >>>>>> Let's > >>>>>> encrypt certificate renewal failed" > >>>>>> > >>>>>> Note that with infra things are moving fast and the documentation, > >>>>>> rarely > >>>>>> used, can be deprecated in few years or even months. I did not say > we > >>>>>> should not have ;) > >>>>>> > >>>>>> Also, for simple things like lagging apps., you can't do much but > >>>>>> asking > >>>>>> on Infra HipChat room (not ML , they don't like) or even ask for > >>>>>> service > >>>>>> when you must: https://issues.apache.org/jira > >>>>>> /servicedesk/customer/portal/ > >>>>>> 1/create/3 > >>>>>> > >>>>>> Jacques > >>>>>> > >>>>>> > >>>>>> > >>>>>> Le 07/01/2018 à 16:56, Michael Brohl a écrit : > >>>>>> > >>>>>> BTW, do we have documentation somewhere which explains who is > >>>>>>> responsible > >>>>>>> for these services, how they work, where to lokk what's wrong and > >>>>>>> who to > >>>>>>> inform if there are issues? > >>>>>>> > >>>>>>> To me this is not clear for some of the services (like publishing > the > >>>>>>> website, fisheye, GitHub sync, ...) , but I admit that I did not > try > >>>>>>> very > >>>>>>> hard to find information about it. > >>>>>>> > >>>>>>> Thanks, > >>>>>>> > >>>>>>> Michael > >>>>>>> > >>>>>>> > >>>>>>> Am 07.01.18 um 16:29 schrieb Pierre Smits: > >>>>>>> > >>>>>>> It seems that is not the only service lagging in providing correct > >>>>>>>> results. > >>>>>>>> The same applies to fisheye. See > >>>>>>>> https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk > >>>>>>>> > >>>>>>>> > >>>>>>>> Best regards, > >>>>>>>> > >>>>>>>> Pierre Smits > >>>>>>>> > >>>>>>>> V.P. Apache Trafodion > >>>>>>>> > >>>>>>>> On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb < > >>>>>>>> [hidden email]> > >>>>>>>> wrote: > >>>>>>>> > >>>>>>>> Hey folks, it seems we still have this delay in our git account. > Any > >>>>>>>> > >>>>>>>>> idea how to resolve this and why does it keep happening? > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>> > >>> > >> > > > |
Re: github and git repo still behind subversion
|
Administrator
|
Thanks Deepak,
Completely forgot about that Jira :/ Taher, I think it's a good question to ask at INFRA-15806 Jacques Le 08/01/2018 à 08:04, Taher Alkhateeb a écrit : > Hi Deepak, > > Great! at least the mystery is out. Thank you for the clarification. > > Can we trigger a manual sync ourselves or is this something affecting all > projects and thus only available to infra? I will follow up on that JIRA > meanwhile. > > On Jan 8, 2018 9:38 AM, "Deepak Dixit" <[hidden email]> > wrote: > >> There are some issue at infra level in pussub service that sync svn with >> github. Due to this svn to github auto synching not working. >> Infra team is looking into it.Here is the issue for pubsub sync >> https://issues.apache.org/jira/browse/INFRA-15806 >> >> Admin team did manual sync and now its updated till recent commit, still >> new commit will not sync automatically. >> >> Thanks & Regards >> -- >> Deepak Dixit >> www.hotwaxsystems.com >> www.hotwax.co >> >> On Mon, Jan 8, 2018 at 11:46 AM, Deepak Dixit < >> [hidden email]> wrote: >> >>> Oops here is correct link >>> https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-15686 >>> >>> http://markmail.org/message/2vy3tprutqe5hqti >>> http://markmail.org/message/ange7ygquw7vc22v >>> >>> >>> Thanks & Regards >>> -- >>> Deepak Dixit >>> www.hotwaxsystems.com >>> www.hotwax.co >>> >>> On Mon, Jan 8, 2018 at 11:42 AM, Deepak Dixit >> <deepak.dixit@hotwaxsystems. >>> com> wrote: >>> >>>> Its already reported >>>> https://f.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-15686 >>>> >>>> Thanks & Regards >>>> -- >>>> Deepak Dixit >>>> www.hotwaxsystems.com >>>> www.hotwax.co >>>> >>>> On Mon, Jan 8, 2018 at 4:08 AM, Jacques Le Roux < >>>> [hidden email]> wrote: >>>> >>>>> AFAIK, we don't have a Jira about that. >>>>> >>>>> For Infra issues, we are requested to pass by >>>>> https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3 >>>>> or for quick things Hipchat room. >>>>> >>>>> Maybe though for such a long term request (documentation) the infra ML >>>>> can be used (but I think Jira is easier for both side) >>>>> >>>>> I fear it could eventually be a karma issue (not enough rights, only >>>>> infra have) but we can't know w/o asking and karmas can evolve at the >> ASF... >>>>> Jacques >>>>> >>>>> >>>>> Le 07/01/2018 à 21:11, Taher Alkhateeb a écrit : >>>>> >>>>>> If anyone has information to share that would be great, or at least as >>>>>> Michael pointed out if you know any documentation anywhere that can >>>>>> help us identify how mirroring is done so we can resolve the issue >>>>>> ourselves in the future then we can resolve this more quickly. >>>>>> >>>>>> Perhaps we should start a new JIRA with infra but I'm not sure. Is >>>>>> that appropriate or do we have a pending JIRA already? >>>>>> >>>>>> On Sun, Jan 7, 2018 at 9:17 PM, Pierre Smits <[hidden email]> >>>>>> wrote: >>>>>> >>>>>>> Similarly to the OFBiz project, INFRA is for the greater part staffed >>>>>>> with >>>>>>> volunteers (but I may have outdated insights). More often than not, >>>>>>> and due >>>>>>> to the inability to enforce volunteers (with commitments beyond the >>>>>>> project) to take action on something they do not desire) this leads >> to >>>>>>> a >>>>>>> technical debt regarding documentation. Also like our project. >>>>>>> >>>>>>> Only one volunteer needs to step up to take the action, either to >>>>>>> update >>>>>>> the documentation at INFRA (beyond our control), or in our confluence >>>>>>> to >>>>>>> help our volunteers interacting with INFRA. >>>>>>> >>>>>>> Best regards, >>>>>>> >>>>>>> Pierre Smits >>>>>>> >>>>>>> V.P. Apache Trafodion, >>>>>>> PMC Member Apache Directory >>>>>>> >>>>>>> On Sun, Jan 7, 2018 at 5:36 PM, Jacques Le Roux < >>>>>>> [hidden email]> wrote: >>>>>>> >>>>>>> So far I simply got to the Infra HipChat room and asked there. >>>>>>>> Very successful most of the time, but not documented apart some >>>>>>>> messages I >>>>>>>> sent to this ML and bookmarks I kept on them for myself, like "[FYI] >>>>>>>> Let's >>>>>>>> encrypt certificate renewal failed" >>>>>>>> >>>>>>>> Note that with infra things are moving fast and the documentation, >>>>>>>> rarely >>>>>>>> used, can be deprecated in few years or even months. I did not say >> we >>>>>>>> should not have ;) >>>>>>>> >>>>>>>> Also, for simple things like lagging apps., you can't do much but >>>>>>>> asking >>>>>>>> on Infra HipChat room (not ML , they don't like) or even ask for >>>>>>>> service >>>>>>>> when you must: https://issues.apache.org/jira >>>>>>>> /servicedesk/customer/portal/ >>>>>>>> 1/create/3 >>>>>>>> >>>>>>>> Jacques >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Le 07/01/2018 à 16:56, Michael Brohl a écrit : >>>>>>>> >>>>>>>> BTW, do we have documentation somewhere which explains who is >>>>>>>>> responsible >>>>>>>>> for these services, how they work, where to lokk what's wrong and >>>>>>>>> who to >>>>>>>>> inform if there are issues? >>>>>>>>> >>>>>>>>> To me this is not clear for some of the services (like publishing >> the >>>>>>>>> website, fisheye, GitHub sync, ...) , but I admit that I did not >> try >>>>>>>>> very >>>>>>>>> hard to find information about it. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> Michael >>>>>>>>> >>>>>>>>> >>>>>>>>> Am 07.01.18 um 16:29 schrieb Pierre Smits: >>>>>>>>> >>>>>>>>> It seems that is not the only service lagging in providing correct >>>>>>>>>> results. >>>>>>>>>> The same applies to fisheye. See >>>>>>>>>> https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Best regards, >>>>>>>>>> >>>>>>>>>> Pierre Smits >>>>>>>>>> >>>>>>>>>> V.P. Apache Trafodion >>>>>>>>>> >>>>>>>>>> On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb < >>>>>>>>>> [hidden email]> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> Hey folks, it seems we still have this delay in our git account. >> Any >>>>>>>>>>> idea how to resolve this and why does it keep happening? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |